Related
Hi Everyone,
I thought I'd create a thread for this issue as it seems to be happening at an alarming frequency as of late. Here are some other threads for reference:
http://forum.xda-developers.com/showthread.php?t=1038768&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1035464&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1034261&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1029474&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=991206&highlight=recovery+mount+open
http://forum.cyanogenmod.com/topic/...overy++mount++open__fromsearch__1#entry172534
If you're currently experiencing this issue, I'd like to get some information about your device to look for any trends or similarities:
1) Do you have a G2 or a DZ?
2) Which ROM was last running on your device?
3) Do you have the ENG HBOOT installed?
4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
ilostchild said:
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
Click to expand...
Click to collapse
Which version of cwm are you referring to?
The newest recovery that fixes the off charge issue
maybe related:
http://forum.xda-developers.com/showthread.php?t=1044042
ilostchild said:
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
Click to expand...
Click to collapse
Doubt it. Highly.
1)G2
2)CM 7 RC4
3)No eng hboot
4) I may have used rom manager to download roms a couple times as well as flashing roms
DON_58 said:
1)G2
2)CM 7 RC4
3)No eng hboot
4) I may have used rom manager to download roms a couple times as well as flashing roms
Click to expand...
Click to collapse
which cwm?
Im running 3.0.0.5
We have been looking into this issue on IRC for the past week or so. ANYONE WHO IS HAVING THIS ISSUE NEEDS TO STOP BY THE IRC CHANNEL.
We need to get some more info, right now we only have 2 cases to go on.
irc.freenode.net
#G2ROOT
The internal partitions of the emmc on the incredible are actually visible when connecting to your computer, so a lot of really smart folks formatted these partitions in an attempt to "fix" something that wasn't broken.
this resulted in recovery being unable to mount the partition.
i remember a long time ago helping someone troubleshoot through the process, it involved loading recovery, and using parted to partition and format the different blocks. (this thread here: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ i'm -Stevo-, although the problem was slightly different the same thing stands, no ability to mount cache.
Now, it's kind of annoying, i've found EVERY person i've ever dealt with that had this issue either disappears a half hour after you begin helping them, or are not advanced enough to use ADB (IT's gonna be required in this case if the above still stands)
There's a couple courses of action that can be taken here, you can manually try and format the partition using parted, or it could be as easy as opening adb shell and
mke2fs -t -ext3 /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
i dunno, no one ever sticks around enough to try anything.
i couldnt even get someone to give me the output of
ls /dev/block
okay so i decided to live dangerously and recreate this error on my device. I made sure the cache partition was nice and corrupted and got greeted with this wonderful message:
{
"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"
}
Now this not the same situation that ALL people are in, but in this situation i opened adb shell and typed
mke2fs /dev/block/mmcblk0p27
reboot recovery
everything back to normal.
Now this is ONLY if your cache partition alone is corrupted, not if the actual paritions are just gone. in that case you'd want to check /dev/block and see the partitions listed, if they are all there as they should be (mmcblk0p25 mmcblk0p26 and mmcblk0p27) you can try and do the same.
hope this helps anyone.
Some things to remember though:
/cache/recovery/command is usually only invoked if your device is not properly rooted (check the numerous droid, evo, desire threads on this, they all had to restore an official RUU and root again to fix)
if there's nothing to mount in /dev/block have a feeling this is related to the emmc not initializing, in which case...
amazinglarry311 said:
okay so i decided to live dangerously and recreate this error on my device. I made sure the cache partition was nice and corrupted and got greeted with this wonderful message:
Now this not the same situation that ALL people are in, but in this situation i opened adb shell and typed
mke2fs /dev/block/mmcblk0p27
reboot recovery
everything back to normal.
Now this is ONLY if your cache partition alone is corrupted, not if the actual paritions are just gone. in that case you'd want to check /dev/block and see the partitions listed, if they are all there as they should be (mmcblk0p25 mmcblk0p26 and mmcblk0p27) you can try and do the same.
hope this helps anyone.
Some things to remember though:
/cache/recovery/command is usually only invoked if your device is not properly rooted (check the numerous droid, evo, desire threads on this, they all had to restore an official RUU and root again to fix)
I have a feeling this is related to the emmc not initializing, in which case...
Click to expand...
Click to collapse
You should make your own thread. I think this will help many people. Great job bro.
Sent from my HTC Desire Z/G2 using XDA Premium App
Hi !
We have to be carefull not to mix two issues here that might look similar to the user.
In both cases the recovery will give an error that it can't mount recovery.
One is that some partitions are corrupted and this can be fixed by recreating the partition as described by amazinglarry above or by reflshing the stock rom.
The second issue is that the emmc chip fails to initialize and in this case nothing can read or write the emmc. You can check if you have this case by booting into recovery and using adb to get a shell. In the shell do a "cat /proc/kmsg | grep mmc0" (i will reformat this tomorrow).
If you see messages that indicate that the emmc did not initialize, then you are in this boat.
There is currently no cure for this, but we try to find what causes this.
have fun - Guhl
Sent from my HTC Vision using XDA App
I'm glad that this issue is being worked on -- no one should have their phone suddenly brick.
Anyways, check out these IRC logs for more context: http://irclog.netripper.com/G2ROOT/2011/4/26/ (start from the middle)
The MyTouch 4G is also having the same problem, I'll be around here looking for solutions as well as maintaining a thread on the myTouch general side.
This happened to a friend's phone. I tired everything to get it fixed (I made a thread but I don't have the link) and ended up returning it to gat another one. What I'm curious about is how do you enter the partition commands? Is recovery (it was cwm 3.0.0.5 btw) able to provide adb access? If so, I was never able to get that and yes, I know how to use adb and have the drivers.
Sent from my HTC Vision using XDA App
I had the same problem. I started a few threads about it as well and posted everything I did (search my username so I dont fill up the thread) and I never got it fixed. Ended up just getting a new phone instead because it seemed like no one really knew much about the error and how to fix it.
SAAADD!
mke2fs /dev/block/mmcblk0p27
reboot recovery
I have this problem (for the second time actually...I was able to fix it the first time by flashing a 2.x.x.x CWM in EBL and formating the cache in that but no such luck the second time I got this error)
Anyhow I tried the above command for all (25/26/27) and it did not fix my issue...I also tried
cat /proc/kmsg | grep mmc0
to test if I have that fail to intialize issue. But it says that isn't a valid command in adb.
Any help? Also I read flashing PMG15.IMG in EBL fixes this but when I tried that I get the Failed PU error!! I think Im screwed huh?
Had same issue. one difference is that I flashed the rom on top of it and my phone bricked completely.
No hboot,no adb , nothingg
Sent from my HTC Desire Z using Tapatalk
I am sorry for opening this thread.
After 2 days of waiting, it seems that the 3G forum section is useless in terms of helping the ones in need.
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition, and now it seems that my tablet is on first baseband (a backup radio it seems) released with the device which has some issues (wifi signal very crappy)
In fastboot the baseband appears N/A
My request, if someone knows, on which emmc partition is stored the radio i would be very grateful.
Also a dump of that partition would help also.
I cannot flash the radio via fastboot
apia-1231_0.17.0_1205.img
sending 'radio' (16384 KB)...
OKAY [ 2.001s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.018s
Also trying to dump the partition on the usual mount point results this
dd if=/dev/block/platform/sdhci-tegra.3/by-name/RDO of=/sdcard/RDO.img
/dev/block/platform/sdhci-tegra.3/by-name/RDO: cannot open for read: No such file or directory
In theory i should be able to restore by using the dd on the emmc partitions, but i don`t know which one it is.
ls /dev/block/mmcblk*
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
In my first look this is what i found, if someone can assist me with this, there are multiple users with this issue, so also others at some moment will be grateful if we fix this.
1) On which partition is the radio stored
2) Can someone dump that partition using dd ?
Again, sorry for creating this post, i don`t usually do things like this (old user, know how the things work around here), but i am a little bit desperate.
Managed to fix partially the issue.
In bootloader the Baseband still appears as N/A
What I did.
1) Mounted radio-tilapia-1231_0.18.0_0409.img
2) Copied the radio_update.zip
3) Rebooted the Tablet in RECOVERY
4) Presse Power Key and Volume Key Plus (first power key, while you keep the power pressed, press the volume key for 2 seconds, release)
5) Select "Apply Update From ADB"
6) Issue the command "adb sideload radio_update.zip
7) Wait till the update goes to end,, and select Reboot system now.
Now when you check in Settings/About Tablet/Baseband, you should have the Baseband which you applied via adb
For those in need, here is the radio_update.zip
http://globula.arctablet.com/Nexus7/radio_update.zip
Still the question remains open, HO KNOWS WHAT PARTITION IS THE ONE FROM THE RADIO ?
Hello
I have exactly the same issue reported by globula neagra.
In my case the issue started just after Nexus came back from Asus repair center with the motherboard replaced. .
As the radio cannot be flashed, the ota procedure fails.
Any idea how to recover the radio partition in order to flash the correct radio image file?
Regards.
My N7 2012 has the same symptoms (Baseband N/A in fastboot) after getting it back from Asus a couple of weeks ago. I believe they replaced the motherboard of my N7 if that matters. I was able to adb sideload the radio from 4.3 then fastboot all factory images from the latest update and then relock. Not sure if I should send it back since it will not install otas on its own, and I will have to adb sideload the radio every update. Thanks op for the info on adb radio update.
Sent from my Nexus 7 using xda app-developers app
My Nexus 7 2012 has the same problem. I could not update OTA and also fastboot update fails, because of Baseband N/A. Now I'm on 4.3 but with old Baseband. I didn't update it, because looks like everything is running.
Before my one was two times in service at Asus. One time they replaced the mainboard.
For sure the solution of globula neagra is a good workaround, but it is very strange that, after the motherboard replacement, you cannot update anymore a standard product with a standard OTA procedure.
Maybe something could be revised in the replacement process.....
flaps1970 said:
For sure the solution of globula neagra is a good workaround, but it is very strange that, after the motherboard replacement, you cannot update anymore a standard product with a standard OTA procedure.
Maybe something could be revised in the replacement process.....
Click to expand...
Click to collapse
UP
Can someone dump that partition using dd, as asked by Globula Neagra?
I don`t understand what exactly you talk about .. radio partitions etc. but if that helps I had a problem with the memory of the tablet: have 32g + gsm N7 and in storage tab it appears only 6gb availabale, so I downloaded nakasig-jwr66y-factory-bdbb7bd7.tgz , extracted the archive and in created folder there was
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-jwr66y.zip
radio-tilapia-1231_0.18.0_0409.img
Using windows 8 I executed in CMD flash-all.bat and the script flashes the radio,bootloader,stock rom and many other things that I did not seen before.I can`t provide a link for download but it is in the forum.I`ll be happy if that can help you solve your problem! Just flash without fear
Blown_ouT said:
I don`t understand what exactly you talk about .. radio partitions etc. but if that helps I had a problem with the memory of the tablet: have 32g + gsm N7 and in storage tab it appears only 6gb availabale, so I downloaded nakasig-jwr66y-factory-bdbb7bd7.tgz , extracted the archive and in created folder there was
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-jwr66y.zip
radio-tilapia-1231_0.18.0_0409.img
Using windows 8 I executed in CMD flash-all.bat and the script flashes the radio,bootloader,stock rom and many other things that I did not seen before.I can`t provide a link for download but it is in the forum.I`ll be happy if that can help you solve your problem! Just flash without fear
Click to expand...
Click to collapse
So it will erase all apps and data on N7?
vndnguyen said:
So it will erase all apps and data on N7?
Click to expand...
Click to collapse
Yes in that case executing the flash-all.bat it will wipe all the data and apps but you can try to manualy flash the radio and the bootloader with that latest version...and like I understand your problem you can`t lose much...still you can`t use your device
@Blown_ouT
I did tried several approaches, and actually what you are saying above broke my device and created the issue with the radio.
The bootloader is saying that my radio partition does not exist anymore, therefore you can not flash something that is not existent, and your method does not work.
Tough, the partition is not vanished it must be there but i think is corrupted somehow.
When i broke the device first time i did this:
1) Update the tablet using the OTA
2) Result was a broken radio
3) Tried to re-flash the tablet using the stand alone pack
-when i did this, i did not wanted to unlock the tablet, still the cmd file runned and erased everything from the tablet but not flashed nothing, which is the most stupid thing since i did not unlocked the device and therefore the restrictions were up (which are supposed to be in theory a non access to erase/write but still google allows you to brick your device with the cmd file without unlocking, but does not allow you to fix it till you unlock it, again VERY STUPID)
-i was able to flash all the files one by one except the radio
globula_neagra said:
@Blown_ouT
I did tried several approaches, and actually what you are saying above broke my device and created the issue with the radio.
The bootloader is saying that my radio partition does not exist anymore, therefore you can not flash something that is not existent, and your method does not work.
Tough, the partition is not vanished it must be there but i think is corrupted somehow.
When i broke the device first time i did this:
1) Update the tablet using the OTA
2) Result was a broken radio
3) Tried to re-flash the tablet using the stand alone pack
-when i did this, i did not wanted to unlock the tablet, still the cmd file runned and erased everything from the tablet but not flashed nothing, which is the most stupid thing since i did not unlocked the device and therefore the restrictions were up (which are supposed to be in theory a non access to erase/write but still google allows you to brick your device with the cmd file without unlocking, but does not allow you to fix it till you unlock it, again VERY STUPID)
-i was able to flash all the files one by one except the radio
Click to expand...
Click to collapse
Hello, just an update about this issue,
I started the RMA procedure and ASUS replaced me the motherboard again (already one had been replaced).
Yesterday i received back the Nexus, nothing had changed, the tablet has exactly the same issue.
At this point, i think there are only three possibilities:
1) all the motherboards used in the Repair center are faulty
2) there is something wrong in the ASUS procedure
3) the problem is not related to the motherboard but is somewhere else
I am very frustrated about this situation, 5 months of tablet and three times in repair center without repairing the issue.
flaps1970 said:
Hello, just an update about this issue,
I started the RMA procedure and ASUS replaced me the motherboard again (already one had been replaced).
Yesterday i received back the Nexus, nothing had changed, the tablet has exactly the same issue.
At this point, i think there are only three possibilities:
1) all the motherboards used in the Repair center are faulty
2) there is something wrong in the ASUS procedure
3) the problem is not related to the motherboard but is somewhere else
I am very frustrated about this situation, 5 months of tablet and three times in repair center without repairing the issue.
Click to expand...
Click to collapse
I do think is an issue on a software level.
Google/Asus don`t want to admit that the updates are "braking" the tablets.
Geez, I have the same problem, I also got my Nex7 GSM from the repair with the new motherboard.
They had one job....
globula_neagra said:
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition, and now it seems that my tablet is on first baseband (a backup radio it seems) released with the device which has some issues (wifi signal very crappy)
In fastboot the baseband appears N/A
Click to expand...
Click to collapse
When ASUS replaced my device's motherboard they reinstalled the factory 4.2 instead of the 4.4.4 it was on at the time. During the 4.3 OTA upgrade the device hung and now the baseband is N/A in the bootloader menu. Trying to flash factory images or just the radio itself obviously doesn't work.
Other than your excellent sideload work-around, have you found a proper fix for the radio partition itself?
globula_neagra said:
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
Click to expand...
Click to collapse
Still the question remains open, HO KNOWS WHAT PARTITION IS THE ONE FROM THE RADIO ?
Click to expand...
Click to collapse
By now it's probably common knowledge to you and others with this problem that when the Nexus 7 3G gets into this state, the radio partition doesn't show up in the list anymore. My tablet broke before I could have a look at what correct partition information looks like, and there isn't much about it on the Internet either. However, these seem to agree:
http://forum.xda-developers.com/showpost.php?p=35103211&postcount=16
http://www.0jl.com/blog/?p=2196
http://forum.xda-developers.com/showthread.php?p=45045265#post45045265
E.g.:
Code:
Device "/ dev / block / mmcblk0p1", the name of "SOS", format emmc, capacity 12M, mount --- storage recovery
Device "/ dev / block / mmcblk0p2", the name "LNX", format emmc, capacity 8M, mount --- storage boot
Device "/ dev / block / mmcblk0p3", the name "APP", format ext4, the capacity of 650M, mount "/ system", the storage system
Device "/ dev / block / mmcblk0p4", the name "RDO", format emmc, capacity 16M, mount --- store radio
Device "/ dev / block / mmcblk0p5", the name "CAC", format ext4, the capacity of 443M, mount "/ cache", storage cache
Device "/ dev / block / mmcblk0p6", the name "MSC", format emmc, capacity 512K, mount --- storage misc
Device "/ dev / block / mmcblk0p7", the name "USP", format, capacity 10M, mount --- storage ---
Device "/ dev / block / mmcblk0p8", the name "PER", format, capacity 5M, mount --- storage ---
Device "/ dev / block / mmcblk0p9", the name "MDA", format, capacity 512K, mount --- storage ---
Device "/ dev / block / mmcblk0p10", the name "UDA", format ext4, capacity 28G, mount "/ data", storage userdata
and
{
"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"
}
IOW, compared to grouper the tilapia has an extra 16M radio partition inserted at mmcblk0p4.
Tablets in this state had this partition corrupted or deleted. Would it be correct to deduce that the problem can therefore be fixed by correctly recreating the partition table and then reflashing the machine?
I'm only familiar with working with Windows partitions and haven't been able to find instructions for recreating the Nexus 7 3G's partition table specifically. Is the above information sufficient for doing that, and what commands are needed? My tablet's currently on 4.2.2 and comes with both fdisk and parted.
Thanks in advance,
Francois
globula_neagra said:
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition
Click to expand...
Click to collapse
This seems to be the common experience with radio partition corruption. It also seems the process that leads to this corruption could involve a corrupt bootloader.
It turns out that both recent factory images as well as at least the 4.3 OTA for the Nexus 7 3G contain a corrupt bootloader, see http://forum.xda-developers.com/nexus-7/general/info-nexus-7-3g-ota-bootloader-corrupt-t3033513. This means whether Android software is being installed manually or automatically, the target machine is potentially exposed to the corrupt bootloader.
Most firmware installs that include a new bootloader and radio software first install the bootloader, then boot into that, then next proceed with installation of the radio software, and then whatever else.
This opens up the possibility that failure to install and activate the new bootloader contributes to corruption of the radio partition when its upgrade is attempted. If I manage to test this once my machine is returned from repairs I hope to update. Any other thoughts or contributions in the meantime will be appreciated. Especially towards fixing the radio partition.
this thread is outdated!
please use this instead:
http://forum.xda-developers.com/one-m9/general/how-to-disable-remaining-write-t3171735
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
this thread is for m9 it will NOT work on m7,m8,or any older devices(or anything other than HTC)
again,dont do this on anything other than m9. any posts stating "i bricked my whatever" will be directed back here,to this first bit of information.
this thread is to help you restore your software status: modified back to software status: original without having to run an RUU. those who have had m7,and m8 are familiar the the tampered flag wich is set when s-on by unlocking the bootloader and installing a custom recovery,kernel,or rom. this thread is the same. it is not a false or hex edited aboot,it is changing the flag that aboot checks to see if your device has been "tampered" with.
unfortunately,HTC has snuck in some evil write protections even on s off devices. as such,it is no longer possible to issue a simple adb command to re-write the flag.
at this time,this thread is for more advanced users. i will try and refine it to be more user friendly,but for now want to get the info out here.
credits
-beaups for schooling me on echo comand protocol,and pointing out that we can still fastboot flash partitions to make permanent changes.
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
- @Mutasek24 for fearlessly testing all commands
- @w3by for finding and testing 00408405 flag location
the usual disclaimers:
-i have tested this on my device,but use this info at your own risk. if it melts your phone into an aluminum gooey mess,crashes your pc,or causes any other issues,its not my fault.
then the most important disclaimer:
*be very careful when editing. accidentally adding or deleting something could change all offests,and leave your device unrecoverably bricked. do NOT use someone elses modified file. p8 is device specific
in other words,if this scares you,and an RUU is available for your device,run the RUU instead.
prerequisites:
-you must be S-OFF
-you must have superuser installed
-you must have adb and fastboot,and working drivers(if required) installed on your machine
this will require the use of a hex editor. for windows,i use HxD
1)copy p8
-open a command window and change to your adb/fastboot directory
-enter the following:
adb shell
su (if needed to get a # prompt)
dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8
exit
exit (if needed to get back to a regular prompt)
adb pull /sdcard/mmcblk0p8
youll now find a copy of p8 in your adb/fastboot folder. transfer it to a safe location (alternately,you could open your internal storage on the pc and drag the file to a different folder)
2)modify p8
-fire up your hex editor and open the mmcblk0p8 file
-scroll down to 00408400. what youll see if this:
the numbers 68 25 32 C6 are a constant.dont mess with them! the fifth digit(location 00408404) is your tampered flag. in some cases,you could find your tampered flag one spot over,at 00408405(more info).
on m9,its commonly a 10,but ive also seen 08 and it really could be anything. we need to change it to a 00.
carefully click in front of then 10,and type a 0. this should overwrite the 1 and change to 00(if you have a "0-other number" youll need to enter 0 twice)
again, be very careful not to add or delete any digits!!!
what you should now see is this:
once your confident its right,save the file as mmcblk0p8mod.img ( adding the file extension is important) to your adb/fastboot directory
3)install your untampered file
in the cmd window,enter:
adb reboot bootloader (this should take you to the white bootloader screen NOT download mode)
fastboot flash pg2fs mmcblk0p8mod.img
fastboot reboot-bootloader
you should now see software status: original
your cmd window should look like this:
Code:
E:\mini_adb\miniadb_m9>[COLOR="Red"]adb shell[/COLOR]
[email protected]_himaul:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]_himaul:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8[/COLOR]
dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8
48510+0 records in
48510+0 records out
24837120 bytes transferred in 5.605 secs (4431243 bytes/sec)
[email protected]_himaul:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]_himaul:/ $[COLOR="red"] exit[/COLOR]
exit
E:\mini_adb\miniadb_m9>[COLOR="red"]adb pull /sdcard/mmcblk0p8[/COLOR]
2986 KB/s (24837120 bytes in 8.122s)
E:\mini_adb\miniadb_m9>[COLOR="Red"]adb reboot bootloader[/COLOR]
E:\mini_adb\miniadb_m9>[COLOR="Red"]fastboot flash pg2fs mmcblk0p8mod.img[/COLOR]
target reported max download size of 536870912 bytes
sending 'pg2fs' (24255 KB)...
OKAY [ 0.609s]
writing 'pg2fs'...
OKAY [ 0.213s]
finished. total time: 0.826s
E:\mini_adb\miniadb_m9>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
other useful threads:
lock/unlock bootloader: http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
change mid: fastbooot oem writemid xxxxxxxxx
change cid: fastboot oem writecid xxxxxxxx
mine
Nice, glad you got it working. I would have rather done this then flash my rom.zip 3 times
an0ther said:
Nice, glad you got it working. I would have rather done this then flash my rom.zip 3 times
Click to expand...
Click to collapse
Lol,I did tell you it was coming
I wanted to come up with some way to avoid the need for hex editing, but couldn't really come up with anything. So I guess it is what it is for now
Do you know if this will need to be done every time something is flashed? Or once s off and we do it once, it sticks with official...?
Edit: worked well
{
"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 HTC One (M9)
Eazy Peazy!
@scotty1223
german translation: http://www.android-hilfe.de/root-cu...-software-status-official-s-off-new-post.html
Rydah805 said:
Do you know if this will need to be done every time something is flashed? Or once s off and we do it once, it sticks with official...?
Edit: worked well
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Just once. Once you're s off the flag is not set
It worked, thanks
If anyone should use another editor like Hex Workshop the position can be displayed as 004083FE (see attached files).
Scotty, first of: all my respect to your work, man. I have been following what you do ever since you started it, I think, but never had any reason to ask you stuff.
Now: I have one question: P8 is pg2fs_ship_signkey.img in the RUU. Can you explain to me why P8 is device specific if its also delivered in a RUU? Is the RUU image maybe just a partial P8?
Oh I should just pull it and chase it through Beyond Compare but its Sunday night, after a long workday and I am lazy.
And oh yea, I wanted to hook up and say hello and thanks and ask if you wouldn't want to discuss the one or other thing occasionally. Not sure you ever visited my firmware threads but if you did, you might have seen that my main goal is to learn and share what I learned and have people educate themselves on everything HTC Firmware. I'd be totally happy to see you linked there. Profit for everyone.
scotty1223 said:
to get a # prompt)
dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8
Click to expand...
Click to collapse
I don't have an m9 yet, but is it safe to copy and paste this command like the old devices to get the p8 from the specific one we would have now? Thanks in advance and for your great work. Wish I could give back something like this. :thumbup:
If you install RUU and puts Officer, thanks!
Enviado desde mi HTC One M9
Many THANKS Sir! Worked like a charm!
Sneakyghost said:
Scotty, first of: all my respect to your work, man. I have been following what you do ever since you started it, I think, but never had any reason to ask you stuff.
Now: I have one question: P8 is pg2fs_ship_signkey.img in the RUU. Can you explain to me why P8 is device specific if its also delivered in a RUU? Is the RUU image maybe just a partial P8?
Oh I should just pull it and chase it through Beyond Compare but its Sunday night, after a long workday and I am lazy.
And oh yea, I wanted to hook up and say hello and thanks and ask if you wouldn't want to discuss the one or other thing occasionally. Not sure you ever visited my firmware threads but if you did, you might have seen that my main goal is to learn and share what I learned and have people educate themselves on everything HTC Firmware. I'd be totally happy to see you linked there. Profit for everyone.
Click to expand...
Click to collapse
hey sneeky,unfortunately i cant explain exactly why p8 shouldnt be shared. my first desire was to simply provide an image,have users download and flash. however,all the ones ive compared have some subtle differences,so i asked beaups his thots on it,and the answer was a clear "no,thats a bad idea. p8 is device specific so users will need to mod their own",so i took his word for it. i know in the past folks have done some shady stuff like that with m7 and m8,and while it may not casue a devestating failure while s off,the prollem may arrise later when they(for whatever stupid reason) turn s on. ive seen hard bricks,soft bricks,and in many cases the reappearance of the tampered flag after a couple of reboots and factory resets. not sure what the actual consequences coulod be in this particular situation.
as for the ruu,i cant really answer that either. ive noticed it also,and my best guess is that the ruu is only having a partial image,or doing a check to mod the image present and not actualy flashing a new one. wish i had a better answer for you than that,lol.
i have been to your firmware threads,and they are a wealth of valuable information. definately hit me up if you ever want to have discussions :highfive:
darkenedpath said:
I don't have an m9 yet, but is it safe to copy and paste this command like the old devices to get the p8 from the specific one we would have now? Thanks in advance and for your great work. Wish I could give back something like this. :thumbup:
Click to expand...
Click to collapse
im not sure what youre asking. if you dont have an m9 yet,what are you wanting to run the command on?
scotty1223 said:
im not sure what youre asking. if you dont have an m9 yet,what are you wanting to run the command on?
Click to expand...
Click to collapse
Sorry. I don't have one yet, but do plan on getting an m9 soon. I'm just trying to keep up and get as much information as I can on this new thing. I re-read the OP feel like a dummy and should have deleted my post. Again, sorry and thanks.
darkenedpath said:
Sorry. I don't have one yet, but do plan on getting an m9 soon. I'm just trying to keep up and get as much information as I can on this new thing. I re-read the OP feel like a dummy and should have deleted my post. Again, sorry and thanks.
Click to expand...
Click to collapse
No prollem. It's definitely good to read and research as much as possible,even prior to acquiring a new device. ?
Sent from my HTC One max
yes it works on my both M9
thx a lot
scotty1223 said:
hey sneeky,unfortunately i cant explain exactly why p8 shouldnt be shared. my first desire was to simply provide an image,have users download and flash. however,all the ones ive compared have some subtle differences,so i asked beaups his thots on it,and the answer was a clear "no,thats a bad idea. p8 is device specific so users will need to mod their own",so i took his word for it. i know in the past folks have done some shady stuff like that with m7 and m8,and while it may not casue a devestating failure while s off,the prollem may arrise later when they(for whatever stupid reason) turn s on. ive seen hard bricks,soft bricks,and in many cases the reappearance of the tampered flag after a couple of reboots and factory resets. not sure what the actual consequences coulod be in this particular situation.
as for the ruu,i cant really answer that either. ive noticed it also,and my best guess is that the ruu is only having a partial image,or doing a check to mod the image present and not actualy flashing a new one. wish i had a better answer for you than that,lol.
i have been to your firmware threads,and they are a wealth of valuable information. definately hit me up if you ever want to have discussions :highfive:
Click to expand...
Click to collapse
I ran a pulled P8 and the pg2fs_ship_signkey.img throug Beyond Compare today and its pretty clear the image from the RUU is only partial. Its a small piece of encrypted stuff that goes into roughly the first third of the large P8, a small set of unencrypted strings that go right at the start and thats it. The rest of the partition is mostly zeroes (empty) and some very few offsets with just some tiny bits of info there, mostly encrypted. One is the tampered flag. It even says "tamper" in plain text before it. If it is that bit, it looks different to what you posted. But that plain text was some sort of clue lol.
The entire section after that encrypted block from ship_signkey is not found in the RUU image.
Worked like a charm thank you
Will tbis lock the device? I want to reset to official but unlocked with s-off. Does that make sense? I read in the re-lock bootloader thread that once re locked you can't set system to RW..
Sent from my 0PJA2 using Tapatalk
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
For this problem i downloaded UL-K013-WW-12.10.1.36-user.zip file from asus site and i installed. But i get an error like "This package is for K013 devices..... bla bla" and i googled and i deleted 2 rows from updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
and new rom installed without any problem. But result was same, Asus logo and gray-or-black screen.
Anyway, i downloaded the older version UL-K013-WW-12.10.1.36_KK-user.zip and i installed
now i just see this message.
AFU: test IFWI BIOS update.
FV File Size is 0x00300260
I cant open recovery menu, I mean
VOLUME+ and Power => NotWorking
VOLUME- and POWER => Not Working
Just Volume(+) plus Volume(-) plus POWER is working, i mean fastboot menu.
Can i install my tablet from this menu? Or what can i do for my tablet? What is your advice guys?
Sorry for my english.
Thanks.
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
it's not related with this thread
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
{
"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"
}
lambdadroid said:
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
Click to expand...
Click to collapse
Hi
thanks for your replay, i tried somethink with fastboot but i didnt success.
I hope somebody can help me.
Thanks again.
pojeck said:
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
Click to expand...
Click to collapse
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
lambdadroid said:
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
Click to expand...
Click to collapse
hi again
as you told me i did and recovery menu is working now.
C:\Temp>cd asus
C:\Temp\asus>
C:\Temp\asus>fastboot flash osloader efilinux.efi
sending 'osloader' (2009 KB)
fname=efilinux.efi...
2009 KB / 2009 KB
OKAY [ 0.085s]
writing 'osloader'...
OKAY [ 0.006s]
finished. total time: 0.094s
C:\Temp\asus>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
OKAY [ 0.001s]
finished. total time: 0.434s
C:\Temp\asus>
Click to expand...
Click to collapse
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
pojeck said:
hi again
as you told me i did and recovery menu is working now.
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
Click to expand...
Click to collapse
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
lambdadroid said:
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
Click to expand...
Click to collapse
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
Click to expand...
Click to collapse
Any idea?
pojeck said:
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Any idea?
Click to expand...
Click to collapse
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
I'm not sure why your device isn't booting anymore. Have you tried a factory reset (you can also do that from TWRP).
Hi
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
Click to expand...
Click to collapse
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
pojeck said:
Hi
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
Click to expand...
Click to collapse
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
lambdadroid said:
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
Click to expand...
Click to collapse
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
pojeck said:
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
Click to expand...
Click to collapse
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
lambdadroid said:
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
Click to expand...
Click to collapse
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
pojeck said:
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
Click to expand...
Click to collapse
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
lambdadroid said:
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
Click to expand...
Click to collapse
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
pojeck said:
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
Click to expand...
Click to collapse
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
lambdadroid said:
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
Click to expand...
Click to collapse
I'm so sorry about that
you can find the correct files in attachment
Thanks...
pojeck said:
I'm so sorry about that
you can find the correct files in attachment
Thanks...
Click to expand...
Click to collapse
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
lambdadroid said:
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
Click to expand...
Click to collapse
Hi
Thank you very much for your kindly notice
I deleted last img files and some pictures.
I'll wait for fixed files, Thanks again.
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