Database Users

From stock to ICS a guide for your U8800-51 or AT&T Impulse 4G

OK I think I cleaned this up a bunch:
Go Here to get all the files, and instructions.txt documentation. (UPDATE: due to dropbox's unreliability, I mirrored all the files to my Google drive public folder. Please use either as long as they work. Feel free to PM me if one goes down.)
ALL users should back up their APNs. Use an APN backup utility to backup/restore.
Code:
[QUOTE=eyeconic]May I make a suggestion?
Actually, EVERYONE should back up their APN. Some user may need to use that backup to restore their APN. I used: [url]https://play.google.com/store/apps/details?id=com.riteshsahu.APNBackupRestore[/url][/QUOTE]
Correct. EVERYONE should backup. Some may meed to restore.
Sent from my U8800-51 using xda-developers app. BAWLZ!
This was discovered by watching the GB Update Forum. Thanks to eyeconic.
Thank You to the Following People. (I hope I didn't forget anyone)
Code:
savagehqfor providing the stock IMG
http://narod.ru/disk/45137127001.c41110d6962cdd0386662315635cdcc4/u8800-51.rar.html
skippedfor instructions on reverting to stock
http://forum.xda-developers.com/showthread.php?t=1589205
KayxGee1for Win7 Roadkil fix
http://forum.xda-developers.com/showpost.php?p=24618284&postcount=2
skippedfor instructions on backing up phone using "Roadkil's DiskImage"
http://forum.xda-developers.com/showpost.php?p=24408417&postcount=3
roadkil.netfor making DiskImage
http://www.roadkil.net/program.php?ProgramID=12
zchuxz3xfor making a Stock to GB Tutorial
http://forum.xda-developers.com/showthread.php?t=1698308
Somcom3Xfor making a Custom GB to Updated GB Tutorial
http://forum.xda-developers.com/showthread.php?t=1844442
Somcom3Xfor making a Updated GB to Aurora ICS Tutorial
http://forum.xda-developers.com/showthread.php?t=1844982
[email protected] providing Browser.apk to fix crashing browser
http://forum.xda-developers.com/showpost.php?p=26917631&postcount=3
hitaxasfor linking to [email protected]'s posting of Browser.apk
http://forum.xda-developers.com/showpost.php?p=31196713&postcount=18
Bad.Fishfor discovering that a factory reset was needed after backing up the phone.
eyeconicfor discovering that some people need to back up APNs.
*************NOT OPTIONAL!*****************
********Backing UP Working u8800-51********
****VERY IMPORTANT! Do in case of FAIL!****
Code:
Make a disk img recovery Using "Roadkil's Disk Image" (and Pink screen)
The procedure is easy and you just take about 8 minutes..
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Download the tool "Roadkil's Disk Image"
1.a Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button.
1.b Connect your phone to PC using USB
2.a Run "Roadkil's Disk Image" (from step 0.a)
2.b Click on the "Store Image" tab.
2.c In "Store Image to" click the combobox and choose "Physical Disk #" ("#" is a number) * If there are more than one "Physical Disk #", then you have to choose the one that is about 3.6gb.. This part is very important.. if you restore a backup from another disk, it will leave your phone unusable.
** To be sure that that Physical Disk you choose is the Huawei u8800-51, You can run the tool again (because it has to refresh) without the phone connected, then check which disks are available. Then, close the tool again, connect the device (in pink screen), run the tool, and check what physical disk was added. But it will be about 3.6gb.
2.d In "target file", save the file as "u8800-51.img" in a folder with more than 4gb of storage available.
** There is no risk for you, as it is just copying data, not writing. **
** The risk is when restoring a backup if you backed up the wrong Disk... **
** If you compress the "u8800-51.img" file into a "rar" file, the size will be about 700 mb, then put it in a safe place. (Like DropBox, and/or multiple hard drives, etc.) **
UPDATE:
I have used this method to restore my phone 3 times without problems, but I'm win7 so I had to use the win7 fix outlined above.
Stock Froyo to Custom GB
Code:
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Make a disk img recovery Using DiskImage (and Pink screen)
0.c Boot into recovery (Vol+ & Power) and do a factory restore.
1.a Download "U8800-51 a Gingerbread.rar"
1.b Extract the Archive.
2.a Transfer the "dload" folder to the root of your sdcard
2.b Turn the phone off completely
2.c Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button. (As though going into Pink Screen) Installation will start.
3.a After the phone finished installing and boots into Android choose the language.
3.b You will notice that you have no signal. This is Fine for Now.
3.c Open File Manager and delete the "dload" folder.
3.d you must also clear the Quick Start (labeled "Fast Boot") in settings> applications, then turn off the phone
4.a Boot Phone into Bootloader (Pink Screen, see step 2.c)
4.b Connect to the pc via USB.
4.c Replace the "boot.img" with the "boot.img" from the "Root para Gingerbread" folder.
5.a Turn on the phone and verify that you have super user.
5.b Turn off phone.
5.c Boot Phone into Bootloader (Pink Screen, see step 2.c)
5.d Replace the "boot.img" with the "boot.img" from the "boot original" folder.
6.a Install ToolBox5irom (step 0.a)
6.b Restore IMEI
6.c Reboot System
** System Should now boot with functional Data. **
Custom GB to Updated GB
Code:
This is a modified stock gingerbread rom for the u8800-51
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Make a disk img recovery Using DiskImage (and Pink screen)
0.c Download "ginger movida v1.1.zip"
0.d Download "CWMv5.5.0.4 recovery.img"
1.a Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button.
1.a Replace "recovery.img" with "CWMv5.5.0.4 recovery.img"
1.b Wipe Battery Stats/cache/dalvik cache in cwm
2.a Install "ginger movida v1.1.zip" using CWM. (From Phone off, Hold Vol+ and Press Power)
2.b Reboot system
** If there is a problem, revert it to stock 2.2 via disk image and start over again. **
Updated GB to Aurora ICS
Code:
This is a modified Aurora ICS Final Build.
Modified Gingerbread must be installed first!
Install at your own risk!
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Make a disk img recovery Using DiskImage (and Pink screen)
1.a Download "Aurora.zip"
1.b Download "gapps-ics-20120429-signed.zip"
1.c Download "UPDATED AURORA.zip"
1.d Download "CWMv6.0.1.0 recovery.img"
1.e Download "Browser.apk" (to fix crashing browser after everything)
2.a Install CWMv6.0.1.0 recovery (from step 1.d) (Install it via pinkscreen or root explorer.)
2.b Wipe Data/battery stats via CWM
3.a Install "Aurora.zip" (from step 1.a) via CWM
3.b Reboot System
3.c Install "UPDATED AURORA.zip" (from step 1.c) via CWM
4.a Reboot system.
4.b Install "gapps-ics-20120429-signed.zip" (from step 1.b) via CWM
4.c Reboot System
5.a Install Browser.apk (from step 1.e)
Note: It may take MANY attempts for it to start, it will constantly reboot. If it takes more than 1/2 hour, than you must restore the disk img recovery.
To enable mass storage install u8800 Aurora drivers and do not toggle mtp. If toggled you need factory reset.
Edit: Tested by me. Must install another keyboard since system keyboard does not exist.
Usb only recognized in recovery, seeking adb fix.
In order for back light you must select auto brightness then un select it.
It begins in Spanish but you need to select language and restart.
Must download poweramp to play music.
No radio
3g may or may not work
Download
You have been warned.
Stable for daily use.
***************OPTIONAL!*******************
*********Reverting to Stock Froyo**********
***ONLY DO THIS IF YOU MESS SOMETHING UP***
Code:
** This will not work on Entel users in Chile as it is a locked restore (it is for at&t users only)- **
100% of the time, You should always backup anything you change. Especially if you don't know what the change will do.
This instructional will help you recover from screwing up your phone (assuming you didn't make a backup image before messing with it.)
Instructions:
0.a Download "DiskImage_1_6_WinAll_Setup.exe"
0.b Use "LockDismount0300.zip" in case of WIN7 problems (see bottom of document)
0.c Download "U8800-51.rar" (about 400mb but its compressed, its really 3.9gb)
0.d Extract "u8800-51.img" from "U8800-51.rar" (Fail to do this and brick your phone)
1.a Open the tool "Roadkil's Disk Image" (from step 0.a)
1.b Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button. (This puts you in Pink Screen)
1.c Connect to PC using USB.
2.a Run "Roadkil's Disk Image" (from step 0.a)
2.b Click on the "Write Image" tab.
2.c In "Write Image to" click the combobox and choose "Physical Disk #" ("#" is a number)
** If there are more than one "Physical Disk #", then you have to choose the one that is about 3.6gb. **
** This part is very important.. **
** If you use a backup from another disk, it will leave your phone unusable. **
** To be sure that that Physical Disk you choose is the Huawei u8800-51, You can run the tool again (because it has to refresh) without the phone connected, then check which disks are available. **
** Then, close the tool again, connect the device (in pink screen), run the tool, and check what physical disk was added. But it will be about 3.6gb. **
3.a In "source file", choose the file "u8800-51.img" that you Extracted from u8800-51.rar (in step 0.d) (remember it is about 3.9gb and extension is ".img")
3.4 Press Write Image.
3.5 After it is 100% ready, disconnect and do a factory reset and you will have 3g working.
** If you were smart enough to have backed up your IMEI at some point, you can install "ToolBox5iromV1.0.4.2.apk" and restore it at this point. **
** If you were smart enough to have backed up your phone prior to messing it up, you can replace any use of "u8800-51.img" in this instructional with your backup image. **
** I already went through one phone because I wasn't smart enough to do backups. Learn frommy mistakes. **
** This will not work on Entel users in Chile as it is a locked restore (it is for at&t users only)- **
*** FOR THE USERS ON WIN7 HAVING TROUBLE WITH "Roadkil's Disk Image" ERROR ***
4.a Download LockDismount to fix the issue (see step 0.b)
4.b Run LockDismount (Run compatibility XP3)
4.c Select the necessary 3.69 drive described above (check multiple times to ensure you're selecting the right drive, for me it was Physical Drive 1)
4.d Click Lock
4.e Keep LockDismount open
4.f Run "Roadkil's Disk Image" (from step 0.a) and then go through the downgrade process. (Start with step 2.a)
Error should be fixed now!
*** FOR THE USERS ON WIN7 HAVING TROUBLE WITH "Roadkil's Disk Image" ERROR ***
Please let me know if I missed anything.

your missing all the roms except for aurora btw.

Somcom3X said:
your missing all the roms except for aurora btw.
Click to expand...
Click to collapse
Yeah. Lol forgot that Dropbox says 14 more hours to complete sync.

Wow!
Sent from my u8800-51 using xda premium

Somcom3X said:
Wow!
Sent from my u8800-51 using xda premium
Click to expand...
Click to collapse
Okay all of the files finished uploading.

Updated aurora info.
Sent from my u8800-51 using xda premium.

Somcom3X said:
Updated aurora info.
Sent from my u8800-51 using xda premium.
Click to expand...
Click to collapse
Do I need to make any changes to my files/instructions, then?
Oh I see. You linked to my thread. Cool, Thanks.

OK. Here it is (so far...)
I backed up my imei. (5irom)
I backed up my Phone (Roadkil's DiskImage)
I installed GB (data didn't work after everything, so i said screw it and: )
Installed Updated GB. (After that my GF called and I couldn't install ICS right away, but phone and data was working.)
Going to install ICS now.

BTW Wifi was working too.
...And just finished. Everything seems to be working now.

Did you install?

Somcom3X said:
Did you install?
Click to expand...
Click to collapse
Yup. Also edited my build.prop so my device shows as U880-51 instead of pro...
{
"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"
}
Sent from my U8800-51 using xda app-developers app

interf sist error
Hello, :good:
thanks for the guide and roms from our device.
I installed the rom ICS on my u8800-51 from Brasil, but when I change the language to Portuguese the app "Interf sist" closes. Run ok only in English. Exists any correction for this problem?

Danielregis said:
Hello, :good:
thanks for the guide and roms from our device.
I installed the rom ICS on my u8800-51 from Brasil, but when I change the language to Portuguese the app "Interf sist" closes. Run ok only in English. Exists any correction for this problem?
Click to expand...
Click to collapse
I am sorry. I don't know much about anything non-english. I am just a typical english-only American. (Much to my chagrin.) I only gathered up guides others had made an put them together. You may have better luck asking in the forum specific to the Android version you installed up to. I can only share my own experience.
Sent from my U8800-51 using xda app-developers app

Danielregis said:
Hello, :good:
thanks for the guide and roms from our device.
I installed the rom ICS on my u8800-51 from Brasil, but when I change the language to Portuguese the app "Interf sist" closes. Run ok only in English. Exists any correction for this problem?
Click to expand...
Click to collapse
try to uncheck 24 hours format after changing the lenguage , in settings -> date and time.

I made a couple bootanimations
http://forum.xda-developers.com/showthread.php?t=1899090

[bootanimation] u8800-51
I made this Bootanimation in Powerpoint. I like it, so I thought I'd share.
U8800-51 bootanimation.zip

Thanks! Used it to unbrick my Ideos X5 PRO!
Thank you very much!

You unbricked a pro using a -51 rom?

freezes after dload reboot
phone reboots then freezes on startup going from stock to gb.... any suggestions?

there's anyone found any solution to the white screen in facebook and gmail?

Incredible!!! Touchscreen firmware updated

I called one day the Touchscreen USSD #removed for n00bs and I don't know that this destroy you touchscreen #
but i pressed the UPDATE button DONT TRY and.... touchscreen doesnt work ... after... Update completed!!! Touchscreen works!!!
Is this UPDATE button harmful as update Camera firmware, or is will update a bit of touchscreen files for Android?
It works for me but Don't Try it!! I does't will have a touchscreen series brick on XDA-developers
If this Update butten too harmfull, please remove this therad
Please help...

i'm the victim
I think doing that is harmful!! coz it had killed my touchscreen after update fail!!
still lookin for soln!
but by the way! thanx for ur warning!

SOLUTION!!!!!!!
Rutayuga91 said:
I think doing that is harmful!! coz it had killed my touchscreen after update fail!!
still lookin for soln!
but by the way! thanx for ur warning!
Click to expand...
Click to collapse
-Solution-
Before we start, make sure you have Java, if not download from here: http://java.com/en/download
I did the touch screen firmware update on my old S5570, i deliberately took battery out during update as i couldnt care less about the phone and wanted a challenge; and sure enough it was dead... But wait... I managed to successfully fix it.... how?
Well
1. Put a custom recovery on your phone (Preferably CWM) - On my samsung you put it into download mode and flash through odin
2. Download ANY custom ROM for your device (.zip format)
3. Open the downloaded zip on your computer, navigate using WinRAR to /system and find the file build.prop, open that file with WordPad, not Notepad but WORDPAD. Find where it says "persist", and there will be a few that start with that, go to the last line and insert:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
This enables USB Debugging by default, I'll explain why you need this later,
Ok save the build.prop and stick it back in the ZIP archive, now download this: https://www.mediafire.com/?omdol91672ieenr
Extract contents to Java directory C:/Program Files (x86)/Java/<Java>/bin (or C:/Program Files/Java/<Java>/bin for 32-bit)
Run cmd and type cd C:/Program Files (x86)/Java/<Java>/bin
(eg "cd C:\Program Files (x86)\Java\jre7\bin")
Place your modified .zip in the /bin folder and name as "rom.zip"
Run sign_file.bat
There should be a rom_signed.zip file in the /bin directory
Now put your phone in recovery and Mount USB storage, drag your "rom-signed.zip" in the root directory, I imagine you'd know how to flash it, but remember to wipe data and cache before hand
Now here's the fun bit
Reboot phone after ROM is installed, 1st boot may take a while
Plug USB in to your computer and download ADB: http://androidarea51.com/downloads/adb.zip
Extract to C drive, now open CMD and type cd.. and cd.. again, then type adb devices, hopefully your phone's serial should appear, if not you have either not got drivers installed or you have done something wrong
So you see your serial number beside adb devices? Great
Now download this: http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp
^^ This requires USB Debugging ^^
And run it, press a button on your phone and it should appear on your pc screen, using your mouse run through the setup proccess, once done open dialer and press "*#2663#" and press Update, then after reboot your phone and...
Touchscreen fixed successfully xD
This worked for me anyway, sorry if some of the instructions are hard to follow, it's my first tutorial so sorry, but please reply if you need any help

Hi, I was trying to follow your tutorial but when I try to install the rom "signed" CWM says that there's an error, I already tried with different recoveries and in some cases it says that the MD5 doesn't exist or the file is not signed or that the rom-signed.zip file can't be opened. I'm using CWM 6.0.4.5 and twrp 2.7.1.0. but I can't install the rom.

Try to recopy
lalo69 said:
Hi, I was trying to follow your tutorial but when I try to install the rom "signed" CWM says that there's an error, I already tried with different recoveries and in some cases it says that the MD5 doesn't exist or the file is not signed or that the rom-signed.zip file can't be opened. I'm using CWM 6.0.4.5 and twrp 2.7.1.0. but I can't install the rom.
Click to expand...
Click to collapse
Hi. Have you tried to recopy the ROM zip file to your sdcard? This usually happens to me also. Maybe the zip was corrupted while copying it from the PC to your sd card. Try to recopy the ROM.

failed to update.
pcwiztech said:
-Solution-
Before we start, make sure you have Java, if not download from here: http://java.com/en/download
I did the touch screen firmware update on my old S5570, i deliberately took battery out during update as i couldnt care less about the phone and wanted a challenge; and sure enough it was dead... But wait... I managed to successfully fix it.... how?
Well
1. Put a custom recovery on your phone (Preferably CWM) - On my samsung you put it into download mode and flash through odin
2. Download ANY custom ROM for your device (.zip format)
3. Open the downloaded zip on your computer, navigate using WinRAR to /system and find the file build.prop, open that file with WordPad, not Notepad but WORDPAD. Find where it says "persist", and there will be a few that start with that, go to the last line and insert:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
This enables USB Debugging by default, I'll explain why you need this later,
Ok save the build.prop and stick it back in the ZIP archive, now download this: https://www.mediafire.com/?omdol91672ieenr
Extract contents to Java directory C:/Program Files (x86)/Java/<Java>/bin (or C:/Program Files/Java/<Java>/bin for 32-bit)
Run cmd and type cd C:/Program Files (x86)/Java/<Java>/bin
(eg "cd C:\Program Files (x86)\Java\jre7\bin")
Place your modified .zip in the /bin folder and name as "rom.zip"
Run sign_file.bat
There should be a rom_signed.zip file in the /bin directory
Now put your phone in recovery and Mount USB storage, drag your "rom-signed.zip" in the root directory, I imagine you'd know how to flash it, but remember to wipe data and cache before hand
Now here's the fun bit
Reboot phone after ROM is installed, 1st boot may take a while
Plug USB in to your computer and download ADB: http://androidarea51.com/downloads/adb.zip
Extract to C drive, now open CMD and type cd.. and cd.. again, then type adb devices, hopefully your phone's serial should appear, if not you have either not got drivers installed or you have done something wrong
So you see your serial number beside adb devices? Great
Now download this: http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp
^^ This requires USB Debugging ^^
And run it, press a button on your phone and it should appear on your pc screen, using your mouse run through the setup proccess, once done open dialer and press "*#2663#" and press Update, then after reboot your phone and...
Touchscreen fixed successfully xD
This worked for me anyway, sorry if some of the instructions are hard to follow, it's my first tutorial so sorry, but please reply if you need any help
Click to expand...
Click to collapse
sir it always fails to update. any solution? im using galaxy pocket.

sumtingswong said:
sir it always fails to update. any solution? im using galaxy pocket.
Click to expand...
Click to collapse
What fails to update?
The ROM installation or Touchscreen?

Finally
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
---------- Post added at 08:33 AM ---------- Previous post was at 08:22 AM ----------
pcwiztech said:
What fails to update?
The ROM installation or Touchscreen?
Click to expand...
Click to collapse
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.

sumtingswong said:
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
Click to expand...
Click to collapse
Why do you want to do this - there is no benefit and a strong possibility your touchscreen will no longer work if it goes wrong

marcussmith2626 said:
Why do you want to do this - there is no benefit and a strong possibility your touchscreen will no longer work if it goes wrong
Click to expand...
Click to collapse
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.

sumtingswong said:
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
Click to expand...
Click to collapse
you can try
http://forum.xda-developers.com/showthread.php?t=1505412
the guide is for the galaxy mini but you should be able to adapt it

sumtingswong said:
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
Click to expand...
Click to collapse
Try this ROM, this should contain the touchscreen binary in the kernel fixing the update fail message: http://www.mediafire.com/download/l570r7dm7545m34/explode+rom+build+5.zip

pcwiztech said:
Try this ROM, this should contain the touchscreen binary in the kernel fixing the update fail message: http://www.mediafire.com/download/l570r7dm7545m34/explode+rom+build+5.zip
Click to expand...
Click to collapse
still no luck sir, still says update fail.

sumtingswong said:
still no luck sir, still says update fail.
Click to expand...
Click to collapse
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage

pcwiztech said:
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
Click to expand...
Click to collapse
it only have one option sir, just update.
{
"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"
}
please help me sir.

pcwiztech said:
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
Click to expand...
Click to collapse
sumtingswong said:
it only have one option sir, just update.
please help me sir.
Click to expand...
Click to collapse
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila

pcwiztech said:
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
Click to expand...
Click to collapse
Okay sir, i'll just try all the custom roms.

pcwiztech said:
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
Click to expand...
Click to collapse
after 10 attempts still no luck sir. please advice.

sumtingswong said:
after 10 attempts still no luck sir. please advice.
Click to expand...
Click to collapse
Hi, sorry for delayed reply, It's morning here.
Unfortunately i think the only option will be to replace your phones digitizer, this will cost around £15-£25 from eBay
Unless you can find a boot.img (kernel) that has the touchscreen firmware then that's your only choice.

pcwiztech said:
Hi, sorry for delayed reply, It's morning here.
Unfortunately i think the only option will be to replace your phones digitizer, this will cost around £15-£25 from eBay
Unless you can find a boot.img (kernel) that has the touchscreen firmware then that's your only choice.
Click to expand...
Click to collapse
thanks for your help sir, i really appreciated it. £15 is the price of a 2nd hand galaxy pocket here sir, so i guess i should really saved for it. i guess i should give up now, it's been quite sometime since ive been stressing myself because of this. godbless you sir.

[Q] Nexus 4, USB Debugging with a cracked screen

Right I have UK Nexus 4, running 4.2.2, Developer Mode is enabled, but USB Debugging is not, it is not rooted.
How can I enable USB Debugging mode, without wiping everything on the phone as I need to use a program called MoboRobo before I wipe the phone (I need to backup messages, bookmarks and contacts)
I can't see anything on the screen at all, so if you are able to help and tell me I need to boot into Recovery mode, then pick an option I need to know how many times to press up or down, this is purely as I can't see a single thing on the screen at all.
I've been trying to follow this: http://forum.xda-developers.com/showthread.php?t=2177440
But I've no idea if that's correct for what I need to do (purely enable USB Debugging mode without wiping what's already on the phone)
Sorry if this has been covered, I've tried to search but the only thing that came close was a Nexus 7 where the user could still see the whole screen.

Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?

Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
1] No
2] No
3] No

JuicedToday said:
1] No
2] No
3] No
Click to expand...
Click to collapse
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Click to expand...
Click to collapse
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.

Johmama said:
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.
Click to expand...
Click to collapse
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
{
"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"
}
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.

JuicedToday said:
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.
Click to expand...
Click to collapse
Ok, let's try eliminating possible reasons for your phone not showing up. Try re-entering recovery mode with the steps I provided above, in case it didn't work. I know this will sound stupid, but it's worked for me in the past: try switching which port on your computer that your USB cable is plugged in to. Try a different cable altogether if you have a spare. Oh, make sure you're using a USB 2.0 cable/plug. Sometimes MTP doesn't play nicely and you need to do weird things to get it working.
I've gathered a few database file locations that you might be interested in. I *think* they are correct anyway. I pulled them onto my computer but I can't try to view them right now, it'd have to be this weekend when I could get around to it, as I'm moving and I'd need to get settled first (Internet up and whatnot). I can still help you troubleshoot adb though.
SMS:
/data/data/com.android.providers.telephony/databases/mmssms.db
Click to expand...
Click to collapse
Contacts
/data/data/com.android.providers.contacts/databases/contacts2.db
Click to expand...
Click to collapse
Browser (I'm not exactly sure which browser)
/data/data/com.android.browser/databases/browser.db
Click to expand...
Click to collapse
Once adb is up and running, you'd use these commands to pull the .db file onto your computer:
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Code:
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db
Code:
adb pull /data/data/com.android.browser/databases/browser.db
Those would pull the .db files onto your computer inside of the platform-tools folder. Again, I'm not sure about this, and can't confirm till later in the weekend, but I think to view those on your computer you can download SQLite from here. More importantly, I assume you can just put those .db files into the proper folders on your new phone to restore them. You'd have to figure out the correct folder location depending on your new device, as the manufacturer or carrier sometimes switches them.

Still getting nothing showing under adb devices even after trying several USB ports with a couple of various data cables.
Think it's a lost cause! Guess I'll just have to plump for the screen when I can afford it. Or swap the screen over on my insurance replacement enable USB Debugging then swap the screen back.
Other option would be to sell my replacement, buy the screen and still have a few quid left over.. Choices choices!
Thanks for taking the time and effort though, appreciate it.

Just thought I'd give this one last try. The data at this point isn't of any concern. I need to wipe everything that is on the phone, if that means the OS as well, then that's fine.
Is there a way I can remove my apps, data, messages etc via USB cable without USB Debugging being enabled?
Thank you for your time.:good:

cracked scereen, tried command, debugging alreadfy enabled. says devivce offline. is that because i have no SIM in it>?

Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.

ji_mestone said:
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.
Click to expand...
Click to collapse
Looks like you're hijacking this thread, but just because I'm currently fighting a similar situation...
you can download the recovery image for CWM at http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-mako.img
and then reboot to bootloader, run "fastboot flash recovery cwm.img" (using the file you just downloaded, i usually just drag and drop onto cmd line)
That will get you the recovery installed that will be useful because you don't have to touch the screen.
After that, It's as simple as selecting wipe all. if you can't see the screen, then you'll have to do these steps (after installing CWM):
hold Vol- and Power until it turns off, then keep holding Vol- and push power again.
down, down, power - boots into recovery
down, down, power - gets you to wipe/factory reset page
down x 7, power - confirms wiping all data

[Q] Problem with booting A3000 after deleting a file in /data

hi all
I have a rooted Lenovo A3000 with a 1 GB storage for apps and 12 GB for files
I have a lots of Important files in 12GB storage
before it I installed root explorer and using it as main file explorer
the story started yesterday when one of my friend who think he is a good geek :silly: gave my device to use his homework
after a while he call me and said "I've done a mistake.I deleted a file in /data and after that device didn't work"
I reset it a lot and i factory reset it
but it's not working
i want to install a FUSED rom on my device( you know having 1 GB for apps is boring ) but the only thing i need is my files and my Device
can i use ADB to copy files?
i know i can use adb pull <dest. dir> <pl. dir>
but i don't know does it work with turned off tablet or not
help me to get my files back and probably my Tablet back
all my homeworks ,books and ... unfortunately is in my 12 GB storage
I don't know which file he deleted
thanks for helping

numb95 said:
hi all
I have a rooted Lenovo A3000 with a 1 GB storage for apps and 12 GB for files
I have a lots of Important files in 12GB storage
before it I installed root explorer and using it as main file explorer
the story started yesterday when one of my friend who think he is a good geek :silly: gave my device to use his homework
after a while he call me and said "I've done a mistake.I deleted a file in /data and after that device didn't work"
I reset it a lot and i factory reset it
but it's not working
i want to install a FUSED rom on my device( you know having 1 GB for apps is boring ) but the only thing i need is my files and my Device
can i use ADB to copy files?
i know i can use adb pull <dest. dir> <pl. dir>
but i don't know does it work with turned off tablet or not
help me to get my files back and probably my Tablet back
all my homeworks ,books and ... unfortunately is in my 12 GB storage
I don't know which file he deleted
thanks for helping
Click to expand...
Click to collapse
You can use ADB with root privilegies in so called "META MODE". To access it, completely turn off your tablet, hold POWER KEY, VOLUME UP and VOLUME DOWN simultaneously, when the screen goes on, you can release the POWER BUTTON, but continue holding VOLUME BUTTONS pressed for a couple of secs (or more) until you see a "=> META MODE" writing on the screen.
Then connect to your PC and use ADB PULL to pull your data.
If everything went OK, you can flash your tablet with stock ROM using this totorial

MirXas said:
You can use ADB with root privilegies in so called "META MODE". To access it, completely turn off your tablet, hold POWER KEY, VOLUME UP and VOLUME DOWN simultaneously, when the screen goes on, you can release the POWER BUTTON, but continue holding VOLUME BUTTONS pressed for a couple of secs (or more) until you see a "=> META MODE" writing on the screen.
Then connect to your PC and use ADB PULL to pull your data.
If everything went OK, you can flash your tablet with stock ROM using this totorial
Click to expand...
Click to collapse
thanks
but take a look at this
PHP:
[email protected]:~/Downloads/Android/Linux$ ./adb_Linux devices
List of devices attached
???????????? no permissions
what should i do?

numb95 said:
thanks
but take a look at this
PHP:
[email protected]:~/Downloads/Android/Linux$ ./adb_Linux devices
List of devices attached
???????????? no permissions
what should i do?
Click to expand...
Click to collapse
What gives you this error ?
What ADB command ?

MirXas said:
What gives you this error ?
What ADB command ?
Click to expand...
Click to collapse
first i enter adb devices to see which device is ready to use to connect to it with adb connect
but it gives me this output
???????????? no permissions
i'm a GNU/linux user and tested it in root user and normal user but both give me this error
what is the best way to backup my data?
thanks

numb95 said:
first i enter adb devices to see which device is ready to use to connect to it with adb connect
but it gives me this output
???????????? no permissions
i'm a GNU/linux user and tested it in root user and normal user but both give me this error
what is the best way to backup my data?
thanks
Click to expand...
Click to collapse
now i get this
PHP:
[email protected]:/home/amir/android-sdk-linux/platform-tools# ./adb devices
List of devices attached
???????????? device
but after using adb commands i've get this error
for example
PHP:
[email protected]:/home/amir/android-sdk-linux/platform-tools# ./adb pull /sdcard0/download /home/amir/
remote object '/sdcard0/download' does not exist
but i know the /scard0/download is already existed
another example
PHP:
[email protected]:/home/amir/android-sdk-linux/platform-tools# ./adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
i want to have a shell access to my phone but got this error
another one:
PHP:
[email protected]:/home/amir/android-sdk-linux/platform-tools# ./adb install Easy_Installer.apk
4077 KB/s (1379930 bytes in 0.330s)
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
i wanna install Easy_installer.apk but got this error
another silly problem
this output says anything
i can push but i cannot pull
PHP:
[email protected]:/home/amir/android-sdk-linux/platform-tools# ./adb push /home/amir/test.txt /sdcard0
[email protected]:/home/amir/android-sdk-linux/platform-tools#
[email protected]:/home/amir/android-sdk-linux/platform-tools# ./adb pull /sdcard0/test.txt /home/numb/Desktop/
remote object '/sdcard0/test.txt' does not exist
[email protected]:/home/amir/android-sdk-linux/platform-tools#

any idea

numb95 said:
any idea
Click to expand...
Click to collapse
Have you tried using MTK DROID TOOLS ? It would fully root your device, maybe that would help.
If none helps, I'd try flashing the stock ROM, except for the userdata.img (or something similar).

MirXas said:
Have you tried using MTK DROID TOOLS ? It would fully root your device, maybe that would help.
If none helps, I'd try flashing the stock ROM, except for the userdata.img (or something similar).
Click to expand...
Click to collapse
i just ignore my data and flashing new ROM
i test several tools and methods but no one works
i should collect my data again but as soon as i can i write a full manual for accessing devices when the device is soft-brick
thanks

LENOVO a3000h GETS STUCK AT BOOT.
I rooted my new Lenovo a3000 h Tablet using farmaroot and tried to flash custom roms 2 or three times, but failed. It runs android 4.2.2. It was running fine but then I tried to install custom fonts and everytime it rebooted to change the system fonts. Yesterday I changed font once more but this time it when it tried to reboot it got stuck at Lenovo logo and the signature tune also is not playing completely.
Tried hard reset, done factory reset using power and volume buttons, tried to install update a3000_os_update_20130506 (downloaded from Lenovo India website) but the installation was aborted.
Can I get stock rom for this asian version from somewhere.. or can I flash A3000_A422_003_014_130909_WW_CALL_FUSE ?
KINDLY HELP ME BROTHER TO OVERCOME THIS PROBLEM. THANKS IN ADVANCE !

hariskk said:
I rooted my new Lenovo a3000 h Tablet using farmaroot and tried to flash custom roms 2 or three times, but failed. It runs android 4.2.2. It was running fine but then I tried to install custom fonts and everytime it rebooted to change the system fonts. Yesterday I changed font once more but this time it when it tried to reboot it got stuck at Lenovo logo and the signature tune also is not playing completely.
Tried hard reset, done factory reset using power and volume buttons, tried to install update a3000_os_update_20130506 (downloaded from Lenovo India website) but the installation was aborted.
Can I get stock rom for this asian version from somewhere.. or can I flash A3000_A422_003_014_130909_WW_CALL_FUSE ?
KINDLY HELP ME BROTHER TO OVERCOME THIS PROBLEM. THANKS IN ADVANCE !
Click to expand...
Click to collapse
Yes, you can flash the mentioned firmware.

my Lenovo softbrick
MirXas said:
You can use ADB with root privilegies in so called "META MODE". To access it, completely turn off your tablet, hold POWER KEY, VOLUME UP and VOLUME DOWN simultaneously, when the screen goes on, you can release the POWER BUTTON, but continue holding VOLUME BUTTONS pressed for a couple of secs (or more) until you see a "=> META MODE" writing on the screen.
Then connect to your PC and use ADB PULL to pull your data.
If everything went OK, you can flash your tablet with stock ROM using this totorial
Click to expand...
Click to collapse
Please help
my Lenovo softbrick , how can i do ADB PULL to pull my data before flashing tne new rom

[HOW-TO]Android 8.1 for Z00VD/ZC500TG

Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
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.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"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"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.

Reserved for possible FAQ in the future

@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?

Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.

Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!

Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.

@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV

I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.

@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!

[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.

aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?

ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one

@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.

@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.

JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again

aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.

I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?

Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.

aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.

Deleted