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
Related
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 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.
Hello everyone.
I'm new to rooting, however, I have managed to root my SM-N9005. I followed a long and for me; difficult process, but I got there in the end. Odin, Tar file & SuperSU all led me to where I am now. My friend told me that I should be using Cyanogen Mod; which is installed. But I've noticed a few perplexing issues which I'm hoping you clever guys might be able to help me out with.
1) Since Modding, my SD card is no longer showing up in "My Computer" when I click on the phone icon. It is still there according to the "Storage" options on the phone and it is populated, but not showing up in my computer.
2) We have a number of devices in our house. 10" tablets, 7" tablets & various android phones. All these show up when I go to Google store, however, since the root, mine is nowhere to be found and I have no idea what to do. I cannot add software old or new, unless I go down the torrent route. MY friend told me that I should install "[GAPPS][4.4.x/4.3.x] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's) [2014-06-08]" as this would solve my issue. So I installed it to my SD card, booted up with Vol up, Power on & home button, selected load zip.... = Fail
Look guys, I'm an old man who suffers from dyslexia, I have honestly tried my hardest, but I'm stumped.
I throw myself at your mercy and beg you for help.
Many thanks in advance.
Wulfrune
Wulfrune said:
Hello everyone.
I'm new to rooting, however, I have managed to root my SM-N9005. I followed a long and for me; difficult process, but I got there in the end. Odin, Tar file & SuperSU all led me to where I am now. My friend told me that I should be using Cyanogen Mod; which is installed. But I've noticed a few perplexing issues which I'm hoping you clever guys might be able to help me out with.
1) Since Modding, my SD card is no longer showing up in "My Computer" when I click on the phone icon. It is still there according to the "Storage" options on the phone and it is populated, but not showing up in my computer.
2) We have a number of devices in our house. 10" tablets, 7" tablets & various android phones. All these show up when I go to Google store, however, since the root, mine is nowhere to be found and I have no idea what to do. I cannot add software old or new, unless I go down the torrent route. MY friend told me that I should install "[GAPPS][4.4.x/4.3.x] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's) [2014-06-08]" as this would solve my issue. So I installed it to my SD card, booted up with Vol up, Power on & home button, selected load zip.... = Fail
Look guys, I'm an old man who suffers from dyslexia, I have honestly tried my hardest, but I'm stumped.
I throw myself at your mercy and beg you for help.
Many thanks in advance.
Wulfrune
Click to expand...
Click to collapse
To make this clear.
1) Factory Reset your phone using odin and install latest firmware that can be downloaded here.
2) Flash your phone using odin. Just get rid of Cyanogen Mod first. (Install it later if you want)
3 After flashing stock rom, Check your SD card is it working or not.
4) If you want to root your phone you can go here and download appropriate file( Which is if you download latest firmware, it should be KK 4.4.2)
4) Flash the file using Odin.
5) If ONLY the problem of SD Card still occur, Try this one here.
Troubleshooting
1) If you are in stock rom and you dont have any problem with SDCARD, then it should be the CyanogenMod problem (I'd never install this rom so i don't know). You can ask on CyanogenMod Thread.
@Wulfrune :
in addition to @IzArsha post,
if you have problem with internal SD card, coming from CM/AOSP to TW rom,
you can try this.
IzArsha said:
To make this clear.
1) Factory Reset your phone using odin and install latest firmware that can be downloaded here.
2) Flash your phone using odin. Just get rid of Cyanogen Mod first. (Install it later if you want)
3 After flashing stock rom, Check your SD card is it working or not.
4) If you want to root your phone you can go here and download appropriate file( Which is if you download latest firmware, it should be KK 4.4.2)
4) Flash the file using Odin.
5) If ONLY the problem of SD Card still occur, Try this one here.
Troubleshooting
1) If you are in stock rom and you dont have any problem with SDCARD, then it should be the CyanogenMod problem (I'd never install this rom so i don't know). You can ask on CyanogenMod Thread.
Click to expand...
Click to collapse
Thank you for the reply.
However, please understand that you're talking to someone with ZERO experience of rooting and in a nutshell..... I'm afraid I've almost no idea what you're talking about The way I usually get around this is to follow video advice.
I will try my very best to get around this problem, but it's abundantly clear to me that I'm in over my head and that it was clearly a huge mistake on my behalf messing around with the phone in the first place. I just HATE the way Samsung think that just because I bought their phone that they own a piece of me.
Given my above statement, I will of course understand if you've no wish to spoon feed me through this process..... But if you can be of further help, I will of course, be very grateful.
The main thing is, you had noble intentions and wanted to help and I think you sincerely for that.
antique_sonic said:
@Wulfrune :
in addition to @IzArsha post,
if you have problem with internal SD card, coming from CM/AOSP to TW rom,
you can try this.
Click to expand...
Click to collapse
Thank you for getting back to me. I followed the instructions you outlined step by step, word for word, pay absolute attention to detail and the following id the result:
[email protected]:/ $ su
[email protected]:/ # restorecon -v -R /data/media
SELinux: Loaded file_contexts from /file contexts
SELinus: Skipping restorecon_recursive(/data/media)
[email protected]:/ #
Sadly, still no sign of the SD card in my computer
Any more ideas?
Thanks
Wulfrune
get rid of root and all will be ok :good:
Wulfrune said:
Thank you for getting back to me. I followed the instructions you outlined step by step, word for word, pay absolute attention to detail and the following id the result:
[email protected]:/ $ su
[email protected]:/ # restorecon -v -R /data/media
SELinux: Loaded file_contexts from /file contexts
SELinus: Skipping restorecon_recursive(/data/media)
[email protected]:/ #
Sadly, still no sign of the SD card in my computer
Any more ideas?
Thanks
Wulfrune
Click to expand...
Click to collapse
Okay just forgot root method first. After you flash stock rom, still no Sd card shown on your computer? it might be your driver is not up to date. Download the PC driver here and reboot your pc and connect your phone and see how it goes shall we?
IzArsha said:
Okay just forgot root method first. After you flash stock rom, still no Sd card shown on your computer? it might be your driver is not up to date. Download the PC driver here and reboot your pc and connect your phone and see how it goes shall we?
Click to expand...
Click to collapse
I think I might be running a newer version of the software that is being linked?
{
"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"
}
[/URL][/IMG]
Here's an update on the state of play .
I have upon advice here updated to Samsung USB Driver for Mobile Phones 1.5.29.0.
I have also changed out my 64gb SD and tried a different one. whilst it still didn't show up in my computer, it did enable me to load up Google's stock package, which in turn, via play store app on the phone lets me load apps again.
I have come to the conclusion that Cyanogenmod might not have been the best route for me and that I'd probably be better off without it. I'm pretty sure it may even go a long way to solving the issues I'm having with the SD card not showing up.
So..........
2 things.....
1) Can someone tell me the safe way to remove Cyanogenmod
&
2) Can someone please suggest a replacement that will fully work with the SM-N9005 please?
Many thanks for you help so far.
Wulfrune
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
unzip the following files onto micro-sd card:
http://download.zeroepoch.com/aftv2/5.0.4/boot.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/lk.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/preloader.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/recovery.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/system.root.img.gz
double check file hashes after transfer to micro-sd because micro-sd cards suck
open up an adb shell and run the following commands:
su
rm -rf /data/dalvik-cache/*
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/storage/sdcard1/preloader.img of=/dev/block/mmcblk0boot0
echo 1 > /sys/block/mmcblk0boot0/force_ro
dd if=/storage/sdcard1/lk.img of=/dev/block/platform/mtk-msdc.0/by-name/lk
dd if=/storage/sdcard1/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery bs=1m
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/mtk-msdc.0/by-name/boot bs=1m
dd if=/storage/sdcard1/system.root.img of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m
Click to expand...
Click to collapse
wait 10 minutes or so after last dd command to help ensure cached data is written, or better yet:
zeroepoch said:
<snip> backup the sync program to /data/local/tmp or run the busybox sync applet. I'd say if you don't understand what that means it's probably not for you. There is always the 2 week method to recover so the device is not a complete brick just very annoying to recover.
Click to expand...
Click to collapse
after you're all done with your 10 minute or so wait, or have run your backed up sync pull the power and restart your device.
this is only for brave people or experts right now.
1 reported brick so far, so I guess don't do this unless you're insane like me
Is this working via LAN ADB? Or better use USB ADB?
Can anybody confirm this process? Since my aftv is unrooted again, I have to root it first before I can try this.
i did it via ethernet. actually, part of the reason i attempted this method is because i left my usb a to a cable at a friend's house.
since you're not rooted though, i fail to see how this will be of any use to you....
Sounds like a funny wilde ride
What is the echo 0 and 1 for?
make the preloader writable, then set it back to read-only
My aftv is just in the rooting process
So this is using adb shell. Is this based on a Linux OS or Windows? I have rooted many android devices, but not the Amazon fire.
use whatever OS you like. use whatever adb connection you like. make the files available to your ftv2 however you like, but in that case make sure to modify the dd arguments appropriately. you can even use magic if you like. this is OS agnostic. if you can put files on a micro-sd card and open an adb shell to your rooted ftv2, you can do this.
rester555 said:
So this is using adb shell. Is this based on a Linux OS or Windows? I have rooted many android devices, but not the Amazon fire.
Click to expand...
Click to collapse
I just did it on Windows 10 through cmd prompt. But, I currently have an issue to where after I unplugged the power, plugged it back in, it's not turning on.
did you let the last dd command finish? that's the big one and it takes a bit for it to write. i did it from win 10 as well, last command should look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nope, the instructions didn't say "sync", "reboot" or "1s".
So now what? It's plugged in usb-usb on my laptop, I keep hearing it connect and disconnect every like 15 seconds.
"of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m" is the tail end of the last dd command, you can see the output that it should give you.
did you see that output?
if you're bricked you're probably looking at 2 weeks of writing a new system partition 512 bytes at a time. that's the only method i can think of right now :/
you would basically do the zeroepoch thing, but instead of patches you'd write the whole thing.
xenoglyph said:
"of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m" is the tail end of the last dd command, you can see the output that it should give you.
did you see that output?
if you're bricked you're probably looking at 2 weeks of writing a new system partition 512 bytes at a time. that's the only method i can think of right now :/
you would basically do the zeroepoch thing, but instead of patches you'd write the whole thing.
Click to expand...
Click to collapse
Yeah, I followed it. I entered that command, once it transferred, I unplugged the power and plugged it back in.
So, basically my 3 day old AFTV is bricked and might as well buy a new one?
edit: just read your description of the boot process
it might theoretically be a fairly quick fix if boot partition just needs repairing, for example. if you're interested i'll try putting together a diagnostic tool based on the existing python code being used for rooting right now. if you're willing to test and report back results let me know and i'll start working on it.
dinggus said:
Yeah, I followed it. I entered that command, once it transferred, I unplugged the power and plugged it back in.
Click to expand...
Click to collapse
Did you hash check the files after you copied them to the SD-card?
xenoglyph said:
did you let the last dd command finish? that's the big one and it takes a bit for it to write. i did it from win 10 as well, last command should look something like this:
Click to expand...
Click to collapse
I added a sync after the dd to stock in my guide now so it has time to flush. Probably same applies here. BTW this exact procedure would be my best guess at how to do it using dd. I didn't even think about clearing dalvik but totally makes sense.
so is this method safe?? Atm I´m not sure if it´s worth it.
Don´t want to brick my device.
Xedos9er said:
so is this method safe?? Atm I´m not sure if it´s worth it.
Don´t want to brick my device.
Click to expand...
Click to collapse
The theory behind it all makes sense and @xenoglyph has been able to do it himself successfully so there is some proof that it works. My best guess going from root to stock is that after dd finishes you need maybe 30sec to a minute if you run sync after for it to flush. Although that's between similar images. The sync command no longer works because it's been moved to a new location where with root to stock it's in the same location. You could try running sync first before starting the dd to maybe cache it but that's kind of risky as well. Better would be to copy the sync program to /data/local/tmp so you can run it after the dd is complete. That is likely my best guess why it's broken, it hasn't flushed yet. If that's true maybe using the full flash method would work better starting from the back going forward since the first part might be written already. Though I don't think I'll have time myself to add this option.
If you're willing to live fast and furious then in theory these commands should work and it changes all the necessary partitions. If you do, make sure you wait a few minutes after the system dd command finishes for it to flush to the device. Maybe even 10 minutes to be safe. A bit more explicit would be to backup the sync program to /data/local/tmp or run the busybox sync applet. I'd say if you don't understand what that means it's probably not for you. There is always the 2 week method to recover so the device is not a complete brick just very annoying to recover.
xenoglyph said:
edit: just read your description of the boot process
it might theoretically be a fairly quick fix if boot partition just needs repairing, for example. if you're interested i'll try putting together a diagnostic tool based on the existing python code being used for rooting right now. if you're willing to test and report back results let me know and i'll start working on it.
Click to expand...
Click to collapse
At this point I'll try anything to get the device working again. I can't even connect via adb she'll as it doesn't see the device anymore.
krawhitham said:
Did you hash check the files after you copied them to the SD-card?
Click to expand...
Click to collapse
Yes
zeroepoch said:
The theory behind it all makes sense and @xenoglyph has been able to do it himself successfully so there is some proof that it works. My best guess going from root to stock is that after dd finishes you need maybe 30sec to a minute if you run sync after for it to flush. Although that's between similar images. The sync command no longer works because it's been moved to a new location where with root to stock it's in the same location. You could try running sync first before starting the dd to maybe cache it but that's kind of risky as well. Better would be to copy the sync program to /data/local/tmp so you can run it after the dd is complete. That is likely my best guess why it's broken, it hasn't flushed yet. If that's true maybe using the full flash method would work better starting from the back going forward since the first part might be written already. Though I don't think I'll have time myself to add this option.
If you're willing to live fast and furious then in theory these commands should work and it changes all the necessary partitions. If you do, make sure you wait a few minutes after the system dd command finishes for it to flush to the device. Maybe even 10 minutes to be safe. A bit more explicit would be to backup the sync program to /data/local/tmp or run the busybox sync applet. I'd say if you don't understand what that means it's probably not for you. There is always the 2 week method to recover so the device is not a complete brick just very annoying to recover.
Click to expand...
Click to collapse
What is the 2 week method?
Help! i am not a linux expert!
Do i have to copy and paste all the commands in the Quote at once? (copy and paste of all block) or i have to copy and paste and run line after line (from the Quote) in my command terminal window?