Related
Disclaimer: I cannot guarantee that this process will work for you as it did for me. If something goes wrong I will do everything I can to help you, but you are responsible. This is a guide for the I9000 international version.
If you think your phone is "bricked" or something goes wrong then use this guide to get your phone sorted.
If you would prefer to use Heimdall to flash or you are not using windows then use this guide.
All "" in this guide are for emphasis or highlighting purposes. All commands should be typed excluding these.
Before you ask, if you have any questions about what PIT file you should use then see this and realise that it really makes little to no discernible difference.
What you need (All links are direct download):
Firmware you wish to flash. Generally find them here.
Odin3 v1.85 (Contained in the firmware)
USB Cable
Backups
Ability to get into download mode
>65% Battery
Section 1: Backups
1.1 Backups:
Download the above file now while you backup using:
SMS using "GO sms", "SMS backup and Restore" or "SMS Backup +"(syncs with Gmail).
Apps using "Listables" or other preferred app. Due to a glitch that occurs with most app backups, market links are not maintained on restore, meaning some updates won't work properly. Using listables you can create an XML list on the SD card and later reopen this list. Then simply long press on each item to download again from market, insuring that updates function correctly. Alternatively you can make a html list, email it to your computer and just reinstall everything using the web market, quicker and simpler. If this is not a huge issue for you then I recommend just using "App Backup and Restore".
Contacts using "GO contacts" or other preferred app.
APN using "APN Backup & Restore" (internal SD save, handles duplicates)
Call logs using "Call Logs Backup & Restore" (internal SD save)
[*}Bookmarks using "Backup Bookmarks"
These will all be saved onto the internal SD card which WON'T be wiped during the update process. If you wish to backup your SD card as well, then be my guest.
Section 2: Download Mode
2.1 Download Mode:
In order to install the new firmware, it is imperative that you can get your phone into download mode. To do this, hold the HOME button + the VOLUME DOWN button + the POWER button until this screen comes up:
{
"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"
}
If this button combination does not work then you probably need to install Android Debug Bridge (ADB) (See Appendix: Download Mode via ADB). If it does, go straight to section 3.
Section 3: Updating
3.1 Prepare Odin
At this point the phone should be in download mode, but have it unplugged from the computer. Extract the firmware and run Odin3, it should look like this:
In odin, there is a lot you don't really need to worry about. Just make sure that Re-Partition, Auto Reboot and F. Reset Time ARE ticked.
Click the button that says PIT, navigate to the folder you unzipped the firmware into, select the PIT file. Press the PDA button and select the CODE file. Press the PHONE button and select the MODEM file. Press the CSC button and select the CSC file.
Now (in download mode) plug in your phone. It may take some time for the phone to register with the computer and it may fail. If that's the case then see Appendix: USB Drivers.
Odin should now look like this with the yellow COM representing your phone connected.
3.2 Installing
Be extremely careful while Odin is flashing your device. Interrupting it is a surefire way to produce a $500 paperweight. I recommend holding your breathe and pretending you are a statue til it's done. Once your phone is connected properly and odin is prepared, hit install. This should take around 2-10 minutes depending on your computer etc. Once done, the phone should reboot and voila you now have gingerbread.
Section 4: Recovery
4.1 Start up
Once the phone starts up it should run you through the setup wizard. Go through this process and add gmail account etc. Then proceed to step 4.2.
4.2 Wipe Cache
Wiping the caches will remove any straggling data from previous installs. But don't stress this will only wipe data off the ROM partition area and not the SD card. While the flash has done most of this, sometimes things get left behind and this will clean them up.
Boot phone into recovery mode (Appendix: Recovery Mode)
You should no be in Clockwork Mod:
There are two options that we need to worry about "Wipe data/factory reset" and "Wipe cache partition".
You need to do both of these, in the order above.
Once these are done there should be an option to "Reboot system now". Do this.
Your cache should now be cleared.
4.3 Restoring
Open the market and download the same programs as before and use them to restore your data
Make sure that you turn off "Delete old messages" and notification settings in stock messaging app before restoring SMS.
Note that apps will not maintain a proper link with the market, it is recommended that you download all apps from scratch using the restore list as a reference.
4.3 APN Settings
If you backed up APN earlier then use the backup, alternatively:
Go to Menu --> Settings --> Wireless and Network --> Mobile Networks --. Access Point Names
Delete all present APN's via long press
Press Menu button --> New APN
Enter details appropriate to your provider which you should be able to find by searching for "<provider name> APN settings"
You may have to create more than one APN
Section 5: Extras
5.1 Rooting and Basic Kernel
Further modification usually requires a little something called root permissions. This is equivalent to administrator privileges in windows. While most custom kernels offer this, Chainfire's CF-Root kernel offers close to stock functionality with this feature added. Grab it here. The latest version should work for the firmware in this guide.
Put phone in download
Open odin
Plug phone in
Load kernel file as PDA
Install
This will install Clockwork Mod (CWM) as well. Having root permissions and CWM will help you modify your phone further (if you so desire).
5.2 SpeedMod Kernel
If you want to upgrade the phone just a tad more than download the latest version of Speedmod Kernel. It's a custom kernel that performs a little bit better than stock. To installs it, do the same procedure as above.
This will also install Clockwork Mod (CWM) Recovery.
5.3 Modem
To do this you need to have done step 5.1.
There are a heap of different modems you can use. The modem is basically the actual phone component of the phone that communicates with the network. Here is a list of available modems but not all of them are gingerbread compatible:
Modems
I would recommend downloading this one UGJL2 Modem. Good battery life and good reception. However, stock modems in gingerbread (JVP onwards) have comparable performance. This is only really something you should learn just in case it's more useful in the future.
You may have to adjust the modem to work on the right band. To do so see the end of the original post here: Modems
To install:
Download file
Copy it across to the phone SD card
Boot phone into recovery mode (see Appendix: Recovery Mode)
Navigate to install zip from SD card (see Appendix: CWM Navigation)
Find the zip you put there and select it
Choose Yes
Phone should install modem and reboot.
Appendix:
Recovery Mode:
Volume Up + Home + Power (until first galaxy s startup screen shows then release)
ADB (Appendix: Download Mode via ADB) "adb reboot recovery"
Download Mode:
Volume Down + Home + Power (until download mode screen shows)
ADB (Appendix: Download Mode via ADB) "adb reboot download"
CWM Navigation:
Use volume to go up and down
Power button to select an option
Back to go back
USB Drivers:
If your USB drivers aren't working then you can try reinstalling them with these:
32 Bit Systems
64 Bit Systems
2.2 Download Mode via ADB
To install ADB, download this and extract it to C:\SDK.
In My Computer, navigate to C:\SDK
In that folder there should be a folder labelled "android-sdk-windows", rename it to "SDK2"
In the second SDK2 folder, run "SDK Manager" and, after some time, this should show:
We only need to install the first one so for each item under the first one, click it and to the right click the reject button until your window looks like this:
Press Install
When finished it will ask to restart ADB, press yes.
Press Close
Once it has installed you need to run windows command prompt (press 'Windows key + R' then type "cmd" and hit enter)
Once in command prompt type "cd C:\SDK\SDK2\platform-tools"
Now type "adb reboot download"
You phone should now show this:
Download key combo should work after flashing.
Finished
Thanks to Hardcore and devz3r0, [Ramad], as well as other users in this thread which have helped to make this guide better. Original ADB Guide. Some reference to this guide also.
Please let me know if i have missed anything.
Think this is the most detailed explanation online... Very Usefull... THANKS in the name of noobs...
ha, i see this thread AFTER i flash my phone (just flashed yesterday)
hi,
you forget to leave password for extract the firmware !!
nicx said:
hi,
you forget to leave password for extract the firmware !!
Click to expand...
Click to collapse
It should be 'samfirmware.com'.
Sent from my GT-I9000 using XDA Premium App
The perfect guide. I am almost tempted to Flash mine but I am still too much a coward.
wow this is just what i need.
My girlfriend has been complaining about how slow her stock 2.2 galaxy is going. She is finally going to let me mod it
Is there another download mirror i can get the 2.3.4 fw from instead of hotfile?
cheers.
FarSight87 said:
wow this is just what i need.
My girlfriend has been complaining about how slow her stock 2.2 galaxy is going. She is finally going to let me mod it
Is there another download mirror i can get the 2.3.4 fw from instead of hotfile?
cheers.
Click to expand...
Click to collapse
You will find many firmwares here: http://forum.xda-developers.com/showthread.php?t=1102881 XXJVP is the first on the list and is only 147MB in size.
Thanks for the guide. There was some nervous moments when odin got stuck at factoryfs.rfs and my phone went green but I found http://forum.xda-developers.com/showthread.php?t=839556 and changed the USB port, and all went well.
Before you restore your previously saved precious SMS, make sure to disable the automatially delete older SMS messages because the limit is set to 200 SMS (same goes for MMS, limit of 20).
For SMS backup and restore, you may also use:
SMS Backup & Restore (internal SD save)
SMS Backup + (syncs with Gmail)
APN Backup:
APN Backup & Restore (internal SD save, handles duplicates)
Call Logs:
Call Logs Backup & Restore (internal SD save)
Bookmarks:
Backup Bookmarks
Applications, I did not find a solution that would "link" the apps back to the Market Place, so backing up downloaded apps did not make much sense, it did just speed up the restore. But if they are not linked and know to Market Place, the My Apps link does not do anything useful to me .
Cache clearing:
It is recommended to clear the cache as well after the firmware installation.
The guide says we don't have to tick repartition.
But i think it should, as it's a 3-file firmware.
And if you don't use repartition, there is no need to backup, cause you won't loose data.
Well since the Cache is recommended to be cleared after the flashing, it is recommended to backup. And I ticked the repartition, because I have seen this mentioned here: http://droidangel.blogspot.com/2011/06/guide-how-to-flash-updateupgrade_10.html
Better safe than sorry
Oh and don't forget to disable HSDP after the flashing in case you are fine with 3G UMTS internet speed: http://www.addictivetips.com/mobile...-for-better-battery-life-on-samsung-galaxy-s/
Easiest way for backing up SMS: the app called 'GO SMS'. Much better than the Samsung one. And there's a feature to back up SMS automatically.
Sent from my GT-I9000 using XDA Premium App
mathijs727 said:
The guide says we don't have to tick repartition.
But i think it should, as it's a 3-file firmware.
And if you don't use repartition, there is no need to backup, cause you won't loose data.
Click to expand...
Click to collapse
You don't need to use a pit or re-partition with 1-file or 3-files firmwares, and there is no point in selecting a pit file while having 're-partition' un-checked.
[Ramad] said:
You don't need to use a pit or re-partition with 1-file or 3-files firmwares, and there is no point in selecting a pit file while having 're-partition' un-checked.
Click to expand...
Click to collapse
True, regardless, I changed the guide to include PIT and re-partition. It's just a tad cleaner and some people get pedantic about that. Won't make a difference to those who don't.
jcspecs said:
It's just a tad cleaner and some people get pedantic about that. Won't make a difference to those who don't.
Click to expand...
Click to collapse
I have seen the changes, you need to prepare your self now for questions like 'which pit file must I use ?'
I have also seen that you are using a link from samfirmware, why don't you use the link from Darky's Forum who was the source for this leaked firmware: http://www.darkyrom.com/community/index.php?threads/odin-cwm-base-ficetos-jvp-base-rom.3519/ samfirmware have just downloaded the firmware from Darky's Forum like everybody else and just put it on there forum.
[Ramad] said:
I have seen the changes, you need to prepare your self now for questions like 'which pit file must I use ?'
Click to expand...
Click to collapse
Yay was just about to include a link to your PIT article and a thanks at the bottom for you.
hi
hi i can't find the speedmod-kernel ,i download the link how you said and i extract and when i am going to put them in odin on pda is empty the with speedmod,somebody can help me please!
Try getting the latest version here.
please somebody can help me! i did every thing like said the side and cant put the kernel in pda in odin ,when i start the odin and i put in pda the file with kernel is empty!what i am doing wrong?please help
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?
Hi,
i want to try TWRP to give my tired volume buttons a rest.
i currently have CyanogenMod 10 on nand+dataonext and some others on native-sd (they are not important)
CWM is in a 5M recovery partition.
first, is there a way to just increase the 5M recovery to install TWRP? i'm hoping yes, but i'm thinking no.
second, assuming no, what do i do to change the recovery size?
do i have to backup with CWM, then repartition, then install TWRP, then,
er.. can i recover the CWM backup with TWRP?
are they just different ways to use the same backup file or is there more to it?
The most important information that you did not provide, which bootloader are you on?
Marvlesz said:
The most important information that you did not provide, which bootloader are you on?
Click to expand...
Click to collapse
doh! magldr
gazzacbr said:
doh! magldr
Click to expand...
Click to collapse
Not necessarily doh, I use cLK for example
Since I don't use MAGLDR, I am not sure. But in MAGLDR, you can change the recovery size by editing the flash.cfg file through notepad and reflash. I don't know if this will remove the ROM in NAND or not.
And I think yes, you can restore your back up from CWM on TWRP, but again, I am not certain. You can backup your rom manually using apps in case it didn't work.
Marvlesz said:
Not necessarily doh, I use cLK for example
Since I don't use MAGLDR, I am not sure. But in MAGLDR, you can change the recovery size by editing the flash.cfg file through notepad and reflash. I don't know if this will remove the ROM in NAND or not.
And I think yes, you can restore your back up from CWM on TWRP, but again, I am not certain. You can backup your rom manually using apps in case it didn't work.
Click to expand...
Click to collapse
actually the doh! was not for you, its a Homer Simpson doh! as i should have added it in the post (its in my sig now).
i know about flash.cfg as thats what i used to set the partitions initially.
Marvlesz said:
.And I think yes, you can restore your back up from CWM on TWRP, but again, I am not certain. You can backup your rom manually using apps in case it didn't work.
Click to expand...
Click to collapse
A CWM Recovery backup can be restored (using the same recovery software) after repartitioning the device.
So, you can create the backup with CWM, repartition with DAF.EXE, reinstall CWM, restore backup, flash twrp and make another backup. Whew!
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
@ny_limited: ok, thanks, thats a good plan as this is a 1-off conversion process (well, this week anyway )
and that means that the backups for cwm and twrp are different then.
but reading this thread
http://forum.xda-developers.com/showthread.php?p=36246549
i will need to manually copy any SD build native-sd roms i have from /NativeSD/ and then replace them if they are later than the TWRP (full ext4) backup
(humming to myself "the more i find out, the less i know...")
gazzacbr said:
@ny_limited: ok, thanks, thats a good plan as this is a 1-off conversion process (well, this week anyway )
and that means that the backups for cwm and twrp are different then.
but reading this thread
http://forum.xda-developers.com/showthread.php?p=36246549
i will need to manually copy any SD build native-sd roms i have from /NativeSD/ and then replace them if they are later than the TWRP (full ext4) backup
(humming to myself "the more i find out, the less i know...")
Click to expand...
Click to collapse
A better plan would be to forget twrp for now. Backup everything, make the recovery partition 8-10 MB, restore everything.
Take a holiday.
The new twrp for hd2 in testing looks like will be able to read cwm backups - not ready yet.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Marvlesz said:
Not necessarily doh, I use cLK for example
Since I don't use MAGLDR, I am not sure. But in MAGLDR, you can change the recovery size by editing the flash.cfg file through notepad and reflash. I don't know if this will remove the ROM in NAND or not.
And I think yes, you can restore your back up from CWM on TWRP, but again, I am not certain. You can backup your rom manually using apps in case it didn't work.
Click to expand...
Click to collapse
yes if you reflash it will remove the rom...
ny_limited said:
A better plan would be to forget twrp for now. Backup everything, make the recovery partition 8-10 MB, restore everything.
Take a holiday.
The new twrp for hd2 in testing looks like will be able to read cwm backups - not ready yet.
Doh! again. and another better plan would have been to read this before messing around this morning
anyway, backed up, changed partition sizes, reinstalled, and twrp is ok
took a few goes though and didnt work until i did a task_29
at least i have the right size partition now when the new one arrives (fingers crossed that it is less than 10MB)
something a bit strange, i couldnt flash_image from adb though as it kept saying it can't find recovery partition, which was true, as df couldnt find it either???
i did an update of the recovery through... recovery, hmm, but it worked ok though
where is recovery mounted, or isnt it? the install script just does a cat of /proc/mtd without checking the actual size
EDIT: messages about unable to mount as "@hB", /dev/block/mmcbl10p1 and as auto mount - for some reason its not able to mount the ext4/native-sd...
if i have to manually backup the native-sd partition then i can do that without twrp
twrp uninstalled, back to cwm recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
gazzacbr said:
ny_limited said:
A better plan would be to forget twrp for now. Backup everything, make the recovery partition 8-10 MB, restore everything.
Take a holiday.
The new twrp for hd2 in testing looks like will be able to read cwm backups - not ready yet.
Doh! again. and another better plan would have been to read this before messing around this morning
anyway, backed up, changed partition sizes, reinstalled, and twrp is ok
took a few goes though and didnt work until i did a task_29
at least i have the right size partition now when the new one arrives (fingers crossed that it is less than 10MB)
something a bit strange, i couldnt flash_image from adb though as it kept saying it can't find recovery partition, which was true, as df couldnt find it either???
i did an update of the recovery through... recovery, hmm, but it worked ok though
where is recovery mounted, or isnt it? the install script just does a cat of /proc/mtd without checking the actual size
EDIT: messages about unable to mount as "@hB", /dev/block/mmcbl10p1 and as auto mount - for some reason its not able to mount the ext4/native-sd...
if i have to manually backup the native-sd partition then i can do that without twrp
twrp uninstalled, back to cwm recovery
Click to expand...
Click to collapse
Which twrp? If the one kokotas is working on - it has a problem and cannot mount yet. Soon. If the one Xylograph patched - it cannot restore. If the one from team win - it does not support hd2.
Soon, but not yet...
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Incorrect Partition Sizing Fix
I partitioned my rom slot #1 wrong, I believe. I think I didn't make enough room for Applications. Since I have only 0.93GB left, I am assuming I made the Application area too small, although I have most things installed that I want installed. So, here's my question. If I do a nandroid backup of rom slot #1 and then create rom slot #2 with a larger Application area, can I then restore the slot #1 backup to slot #2 to resolve this issue? Below is a screen print of Storage for reference.
Thanks,
Marc
{
"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"
}
MarcRJacobs said:
I partitioned my rom slot #1 wrong, I believe. I think I didn't make enough room for Applications. Since I have only 0.93GB left, I am assuming I made the Application area too small, although I have most things installed that I want installed. So, here's my question. If I do a nandroid backup of rom slot #1 and then create rom slot #2 with a larger Application area, can I then restore the slot #1 backup to slot #2 to resolve this issue? Below is a screen print of Storage for reference.
Thanks,
Marc
Click to expand...
Click to collapse
What do you mean by "slot #1" and "slot #2"?
And if we're talking about the HD2 here, then making a nandroid backup --> enlarging partitions --> restoring the backup, should give you the extra storage you want.
I seen a lot of Discussion On this topic, and found a really simple way to disable Forced Encryption and it also removes the warning at boot. This in NO WAY is my work at all. I am sharing this [FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher) which was posted by @gladiac. Absolutely make sure you head over to his forum and hit the Thanks button. This works great
Screenshots Below
I have the option to encrypt the phone as you can see circled. I went into system with Root Explorer and was prompted for R/W access and obviously I granted it. Everything is working great!
{
"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"
}
Preparation
Before proceeding, enable Developer options and MAKE SURE USB DEBUGGING IS ENABLED!!!
1. Download fed_patcher_v7-signed.zip and check here to verify the latest version
2. Download [BETA][2015.10.10] SuperSU v2.52 by @Chainfire
3. Download Whatever ROM you are going to use. I am currently running [ROM]【6.0】LightROM - Marshmallow【MRA58K】- 10/08/15
Instructions
1. Backup your SD Card, during this process, everything will be erased during the process
2. Reboot into TWRP, this is important that you actually have TWRP
3. Perform a Full Wipe by doing the following:
Press Wipe
[*] Press Advanced
[*] Click every check Box
[*] Wipe 3x for good measure
[*] Press Home button
[*] Press Wipe
[*] Press Format Data
[*] Type yes in the box to perform the format
[*] Perform this 3x for a good full wipe
4. Reboot TWRP (Do Not Install Super Su Yet)
5. Once Back In Recovery, On the computer, open My computer
6. Navigate to and open the Nexus 6 Drive
7. Drag the Zip files below to your Phone -
1) fed_patcher_v7-signed.zip
2) BETA-SuperSU-v2.50.zip
3) ROM Zip
If You are Having Trouble, take a look at the screen shots below
You Want to make sure you mount data if it is not, and make sure MTP is not disabled! Thanks @jamiejames and @aliasferno
8. Flash your ROM 1st (DO NOT BOOT AFTER FLASHING)
9. Wipe Dalvick Cache/Cache 3x
10. Flash fed_patcher_v7-signed.zip
11. Wipe Dalvick Cache/Cache 3x
12. Flash BETA-SuperSU-v2.52.zip
13. Reboot and Enjoy with no more red error sign during boot and no encryptionhttps://source.android.com/devices/tech/security/verifiedboot/verified-boot.html#user_experience
Supported Devices
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
[*]v2 - Added Motorola Nexus 6 (shamu) support
[*]v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
[*]v4 - Added support for signed boot-images
[*]v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
[*]v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
[*]v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What Do I need To Make This Work?
A supported device (Your nexus 6)
[*]An unlocked bootloader
[*]An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
[*]A recovery that includes busybox (TWRP, CWM)
How Do I Use it?
Follow Instructions above - This is the basic need to know information
[*]Make a thorough, conservative backup of your data if there is any on your device
[*]Go into your recovery (TWRP, CWM)
[*]Flash fed_patcher-signed.zip
[*]If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is It Dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
All Thanks To:
@gladiac - For Putting the OP together for the Nexus 9 and sharing this
[*]@rovo89 - for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
[*]@pbatard - for making (un)mkbootimg (dunno if he is on xda)
good work mate
Danvdh said:
good work mate
Click to expand...
Click to collapse
Thanks Bro...Thanks for the ROM, I saw it's already updating. Thanks
Thanks for this! :good:
Herk718 said:
Thanks for this! :good:
Click to expand...
Click to collapse
No Problem...
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
TY you for this info. Exactly what I was looking for. Thanks a milion
spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I am decrypted, I have super user ...I was able to restore with titanium backup, I will see if I can edit the build.prop or just mount rw
edit: I was able to mount rw successfully in root explorer no issues
simunovic said:
TY you for this info. Exactly what I was looking for. Thanks a milion
Click to expand...
Click to collapse
No problem
Sent from my Nexus 6 using Tapatalk
spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
bdorr1105 said:
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
Click to expand...
Click to collapse
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
spunks3 said:
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
Click to expand...
Click to collapse
It won't work unless you remove root
Sent from my Nexus 6 using Tapatalk
Moved this from the development forum as there is no development, this is not your work, and it is a guide for this; this is better suited to a General forum.
Thread reopened on the basis that this is a guided collection of work.
Ok, this OP is more of a guide on how to use this tool, I am going to edit the OP and redirect it to the Forum that was in the Nexus 6...There was a mis-understanding on my part, I did not realize this was in the Nexus 6 Android Development already, this is just how to run it, and the steps to successfully flash and get rid of the warning before booting Android 6.0 and having a force decrypted set up form boot...
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
atrix4nag said:
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
bdorr1105 said:
atrix4nag said:
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
atrix4nag said:
bdorr1105 said:
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
I do not have the warning at boot doing this method. So yes, you should no longer have the warning
Click to expand...
Click to collapse
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Hucklebury said:
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Click to expand...
Click to collapse
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
bdorr1105 said:
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
Click to expand...
Click to collapse
ok, thanks for the reply. i have tried many times to get rid of that ugly screen without success, ended up going completely stock M.
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