Related
Does anyone know how to fix an EVO that gives this error?
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD
I was flashing firerant's mtd partition to make up more space to install more apps. When I try to reboot my evo it turns on then vibrates 5 times and shuts down. I can get to hboot mode (volumen down + power). On top instead of s-off it changed to s-on. When I try to use command from my mac's terminal it says error: device not found.
I unrooted by flashing a PC36IMG.zip in hboot. Im in stock now. The phone seems to work fine but now the phone does not recognize the memory card (only in hboot mode) or the usb being plugged in. when i plug in the usb to the computer evo does not give me the notification nor charges or the light come on. Then I tried to root it but it's imposible because I still get terminal's error: device not found because the evo's usb is messed up or something. And since there is no notification to mount the memory card to my computer I can't transfer any files to/from evo.
Then I downloaded Unrevoked3 but still it does not do anything for the same reason the usb is not being detected.
Now I am unroot, evo not detecting memory card (when its on) and usb is messed up (when its on and in hboot mode).
Can Anyone please help me out. Maybe there is a zip that I can flash in hboot mode since is the only place my memory card is being read. Terminal commands through USB doesn't work in hboot or fastboot i dont know why.
Thank you so much everyone.
p.s. I am not blaming this on firerant's mod. I am just describing how it happened. I appreciate all devs work. and I am aware of their disclaimer we can brick our devices. Thank you.
pretty sure you fubar'd your internal partions there buddy.
Go get a new phone. Run over it with your car first.
Sent from my PC36100 using XDA App
Yes that's what I think. The partition is fubar'd, so there is no way to fix that?
Thanks for replying.
mrcamposd said:
Yes that's what I think. The partition is fubar'd, so there is no way to fix that?
Thanks for replying.
Click to expand...
Click to collapse
im sure there is but only by someone who knows what the hell they're doing. lol ;-)
can that person come to the RESCUE :/
lol @ the advice on here. I wouldn't exactly say I know what Im doing but I'll try to help anyway.
From a adb shell run 'cat /proc/mtd' and 'cat /proc/partitions' and that should tell you what your partitions look like. If you can copy them on to here.
Edit: Just remembered he had a custom recovery set up to use with it, were you using that to flash it? You'll most likely need that to recognize the partitions.
If you can flash a zip why not give Caulk's "format all" a try this may restore your partitions. I'm far from a dev but seems like i read about this same problem somewhere and they ran calks zip and presto all was well. I tried to find the thread but couldn't, just what I remember they flashed this then rom then kernel then radios. Of course they were rooted ... maybe rename to PC36IMG.zip ....but if you can flash a zip cant see how this would hurt.
xHausx said:
lol @ the advice on here. I wouldn't exactly say I know what Im doing but I'll try to help anyway.
From a adb shell run 'cat /proc/mtd' and 'cat /proc/partitions' and that should tell you what your partitions look like. If you can copy them on to here.
Edit: Just remembered he had a custom recovery set up to use with it, were you using that to flash it? You'll most likely need that to recognize the partitions.
Click to expand...
Click to collapse
cant adb shell in terminal it does not recognize the device. thanks though
ifly4vamerica said:
If you can flash a zip why not give Caulk's "format all" a try this may restore your partitions. I'm far from a dev but seems like i read about this same problem somewhere and they ran calks zip and presto all was well. I tried to find the thread but couldn't, just what I remember they flashed this then rom then kernel then radios. Of course they were rooted ... maybe rename to PC36IMG.zip ....but if you can flash a zip cant see how this would hurt.
Click to expand...
Click to collapse
thank you so much you are a hero... but will try this next time it happens because I went to the sprint store and told them the new update had messed up my phone hahahaha...
thank you all intelligent people i appreciate your help so much. it means a lot to me.
Hi all
My Galaxy Nexus with CM10 a week ago has started to lag a little bit, and the situation was getting worse day by day...
wipe didn't solve anything
so I tried to run some benchmark in order to understand if it's an hardware problem
with androbench I noticed that the write values are ridiculous
what can I do before bring it back to the manufacter?
When did you buy your Galaxy Nexus?
Can you please post a screenshot of the following App: http://forum.xda-developers.com/showthread.php?t=1693704
Maybe you're affected by this bug:
http://code.google.com/p/android/issues/detail?id=39154
Mine has similar results with androbench and is 2 weeks old. I have not deleted any big files also. The gotbrick app says that my emmc chip is unknown.
Sent from my Galaxy Nexus using xda premium
mariosraptor said:
The gotbrick app says that my emmc chip is unknown.
Click to expand...
Click to collapse
Is it a chip of type V3U00M?
You may try to remount /data and /cache (probably also /system) with the discard option and use dd/rm or Forever Gone to erase the empty blocks as suggested beginning at comment #25.
http://code.google.com/p/android/issues/detail?id=39154#c25
ph4zrd said:
Is it a chip of type V3U00M?
You may try to remount /data and /cache (probably also /system) with the discard option and use dd/rm or Forever Gone to erase the empty blocks as suggested beginning at comment #25.
http://code.google.com/p/android/issues/detail?id=39154#c25
Click to expand...
Click to collapse
Yes, is V3U00M. I read the comments there. I will try forever gone. Thank you
Sent from my Galaxy Nexus using xda premium
ph4zrd said:
Is it a chip of type V3U00M?
You may try to remount /data and /cache (probably also /system) with the discard option and use dd/rm or Forever Gone to erase the empty blocks as suggested beginning at comment #25.
http://code.google.com/p/android/issues/detail?id=39154#c25
Click to expand...
Click to collapse
yes, V3U00M!
I'll try the solution with adb (remount, dd and rm) later.
Thank you!
I just finished the forever gone solution. Tbh it is now worst than before.
Androbench took ages to finish and half the results.
So, to summirize. We should not try any solutions like this or via adb or any other that will make the device perform more slowly.
We bought a phone and expect it to work. Google should step up and fix every possible bug out there and ofcourse not introduce new ones.
Sent from my Galaxy Nexus using xda premium
mariosraptor said:
I just finished the forever gone solution. Tbh it is now worst than before.
Click to expand...
Click to collapse
Did you remount /data with -o discard before using Forever Gone?
ph4zrd said:
Did you remount /data with -o discard before using Forever Gone?
Click to expand...
Click to collapse
Nope. The app did not suggest that.
I will reflash the stock omage again.
Sent from my Galaxy Nexus using xda premium
mariosraptor said:
Nope. The app did not suggest that
Click to expand...
Click to collapse
The app isn't made for fixing this problem. It is made for overwriting free space on the sdcard.
So of course this doesn't fix it. The mount option does and is absolutely essential.
By simply using Forever Gone you only tried how bad this can get
mariosraptor said:
I will reflash the stock omage again.
Click to expand...
Click to collapse
This might temporarily help (a wipe of the system, cache and userdata partitions does), at least a little bit.
But it doesn't fix the problem. The phone will slow down again.
Step-by-step guide
1.
Make sure you have a eMMC chip of type V3U00M using this or this app as I mentioned above.
Otherwise it might be possible that the following commands HARD BRICK your phone.
You can also use the following command: cat /sys/class/block/mmcblk0/device/name
2.
Make sure your phone is rooted.
3.
Install and run this app.
This temporarily solves the problem, the phone will eventually begin to slow down again.
Type the following commands in a Terminal or preferably an adb shell:
Code:
[strike]su
mount -o remount,discard /data
dd if=/dev/zero of=/data/tmp.bin
rm /data/tmp.bin[/strike]
It WILL take a long time (up to 3 hours maybe) and your phone might soft-reboot like mine did. Therefore using adb would be better... Some users also reported a speedup when this is done in recovery mode (CWM/TWRP) via adb.
The dd command seems to fail, issuing a message similar to "no space left on device". This is normal as we don't give the command a particular file size so it fills the partition until no space is left on it. (That's what we want to do)
This temporarily solves the problem. After you reboot the remount option is lost and the phone will begin to slow down again.
Btw, you can also use the Forever Gone app instead of the dd/rm commands. So if you don't want to use the command line, apply Step 4 first (using Script Manager), reboot and then run Forever Gone.
4.
To prevent this, add the following code to a script and put it in the init.d folder (if your rom supports it) or use an app like Script Manager to run it on every boot. (Make sure it is started with root privileges!)
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
5.
Profit.
The only phones affected seem to be Galaxy Nexus GSM (i9250) models with the the V3U00M chip for which it is apparently essential to get TRIM/erase/discard commands or whatever for every single block deleted.
The only reported production dates of bad chips are 08/2012, 09/2012 and 10/2012 until now. Maybe chips produced earlier and/or later are also affected.
You can get the production date of you eMMC chip using the following command: cat /sys/class/block/mmcblk0/device/date
Additional information
Google Code Bugreport (already posted above)
Galaxy Nexus Storage Performance Over Time & TRIM
[Q] Why is my Nexus so sluggish?
My Galaxy Nexus is being very laggy...
[Q] Very slow and laggy Nexus
Other guide, some FAQ + patched kernel (for a specific ROM)
LagFix Tool
some eMMC chip types used at the beginning of 2012 (not affected, type VYL00M for GSM Nexus)
Benchmark of this chip on low-mem conditions
Maybe someone can make a flashable zip or something like that for automating this.
If enough people report this problem I might also do it.
I am not responsible for killing little kittens or your girlfriend getting pregnant by that.
Cheers!
5.
Profit.
The only phones affected seem to be Galaxy Nexus GSM (i9250) models produced after September 2012.
For the V3U00M chip it seems to be essential to get TRIM/erase/discard commands or whatever for every single block deleted.
according though to this my phone is not affected. it has been produced 2012-07(july). should i still proceed?
So I guess my sem32g on my toro should be OK. I get random lag and was wondering if that was it. Over 14 GB used but still about 12 GB free.
Sent from my Galaxy Nexus using Tapatalk 2
mariosraptor said:
according though to this my phone is not affected. it has been produced 2012-07(july). should i still proceed?
Click to expand...
Click to collapse
Seems like the date I posted is incorrect, sorry. Since your chip is not affected by the hard brick bug it should be safe to proceed.
ph4zrd said:
Seems like the date I posted is incorrect, sorry. Since your chip is not affected by the hard brick bug it should be safe to proceed.
Click to expand...
Click to collapse
it's ok.
i found my production date from here http://forum.xda-developers.com/showthread.php?t=1519606
i9250 made by samsung. bought it 2 saturdays ago
tiny4579 said:
So I guess my sem32g on my toro should be OK. I get random lag and was wondering if that was it. Over 14 GB used but still about 12 GB free.
Click to expand...
Click to collapse
Nearly all users which reported this problem until now had maguro phones with V3U00M chips, which does not necessarily mean that toro models didn't get problematic eMMC firmware.
You may try the discard mount option anyway.
---------- Post added at 09:31 PM ---------- Previous post was at 09:26 PM ----------
mariosraptor said:
it's ok.
i found my production date from here http://forum.xda-developers.com/showthread.php?t=1519606
i9250 made by samsung. bought it 2 saturdays ago
Click to expand...
Click to collapse
The production date of your eMMC chip may be of interest.
Can you post the output of the following command:
cat /sys/class/block/mmcblk0/device/date
Click to expand...
Click to collapse
ph4zrd said:
Nearly all users which reported this problem until now had maguro phones with V3U00M chips, which does not necessarily mean that toro models didn't get problematic eMMC firmware.
You may try the discard mount option anyway..
Click to expand...
Click to collapse
I'm somewhat scared to brick the device but the emmc check app says that I font have the brick bug. I also have the 11/2011 date.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
I'm somewhat scared to brick the device but the emmc check app says that I font have the brick bug. I also have the 11/2011 date.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=35027577&postcount=41
Probably it's better if you check for other solutions at first, like looking for CPU-consuming processes or doing a complete wipe (including fastboot erase userdata or similar)...
Ok the problem seems partially solved, thank you very much!
The benchmark result is not great, but the phone it's finally usable.
Look at the attachment, Random write is still bad (I think)
But I repeat the phone it's going well.
My chip date ->
Code:
[email protected]:/ # cat /sys/class/block/mmcblk0/device/date
08/2012
my production is as the friends above from the output of the command 08/2012
edit: the script does not seem to work.
when in smanager i select su, boot and then run i get this:
tem/bin/sh '/01discard'
unknown option --0mount: invalid option -0
unknown option --0mount: invalid option -0
monossidoz said:
Look at the attachment, Random write is still bad (I think)
Click to expand...
Click to collapse
According to this thread
http://forum.xda-developers.com/showthread.php?t=1971852
your random write performance is normal. I'm getting similar results.
Great sequential write performance btw!
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.
GiZiM said:
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.
Click to expand...
Click to collapse
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button (shouldn't be more than a couple of minutes). On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Thank you! I will look into this but I would love to fix the cause.
I'm sure this is the issue because I cannot get the phone back into a working state until after doing a full factory wipe.
What would be causing 4.3 roms to corrupt my /userdata? Whatever it is it is happening after the first reboot after I get into the rom.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!
Thanks this is very helpful, I will work on this tonight after work and see what I can come up with.
Right now it is showing as CLEAN but i'm running 4.2.2. Is there anything special to go from 4.2.2 to 4.3?
desktopfusion said:
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!
Click to expand...
Click to collapse
Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
I'm going to give it a go tonight when I get home.
1. So pretty much backup everything, do a complete factory wipe of all data.
2. I'll do a adb push of the .zip for the rom and everything.
3. Flash rom and any other packages needed
4. Run that command see if it comes back clean
5. Reboot go into the rom
6. Reboot, if i get stuck at the Google screen run that script if it's not clean just keep running it?
desktopfusion said:
Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
Click to expand...
Click to collapse
It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs
GiZiM said:
It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs
Click to expand...
Click to collapse
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
Lifesaving string of code.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse
Holy mother of god.
This was a lifesaving string of code. I was convinced that I was going to have to buy a brand new phone. Kudos to you DesktopFusion. Thanks a lot!
Explanation as to why a corrupt userdata partition causes this issue
So, in case anybody was wondering, I would like to explain how I see the issue at hand (corrupt userdata partition).
Upon first boot, the ROM is getting set up and doesn't have any orders to check /userdata because well, there is none on the device. So why waste precious time being redundant (smart coders, right?). So the userdata partition is not checked.
However, now that the second boot is being performed, there is, by default in the system's repertoir, data put in by the user, so the bootloader is told to check the partition containing user data. Since the partition is corrupt, and the free space is technically "modified", it errors up and gets stuck.
I could be wrong, I'm not a developer of any sorts. Just a dude giving my point of view.
I got this trouble too last night. I'm flashing elia's 4.3 custom rom with under 5 gb free space. Got it boot twice,then got stuck at google's logo after trying flashing slim bean gapps. Flashing whole 4.3 stock firmware finally solve this. Maybe there is correlation between upgrading from 4.2.2 without upgrading the bootloader with this problem.
Sent from my Galaxy Nexus using Tapatalk 4
It ended up running for 6hrs and never finished, I did do the -n and it said it was CLEAN but still could not boot into the 4.3 ROM.
So ran it any way for 6hrs and no change as of right now I am unable to boot into ANY 4.3 ROM.
If eMMC was screwed up why can 4.2.2 roms work fine but not 4.3 roms? what's the difference?
desktopfusion said:
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
Click to expand...
Click to collapse
BUMP still no 4.3 love
GiZiM said:
BUMP still no 4.3 love
Click to expand...
Click to collapse
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?
desktopfusion said:
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?
Click to expand...
Click to collapse
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90
GiZiM said:
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90
Click to expand...
Click to collapse
Rats. Falling short of ideas.
I might have missed your answer on whether you've tried flashing a stock Nexus image through fastboot, though.
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.http://forum.xda-developers.com/images/smilies/highfive.gif
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
7175 nailed it. I tried flashing all sorts of different ROMs/gapps/Super SU combinations and tried different wipes/formats to no avail. I wish I would have found the instructions to "fastboot cleanse" the phone 4 or 5 hours ago. I have been reading through forums for several hours today and every suggested fix failed. 7175's fix was spot on for me. My phone was locking up at the Google screen with the lock every time I rebooted after installing a 4.3 ROM.
:highfive:
7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
Thanks for this...
First thought it was an issue with SlimRom, tried different kernels, problem wouldn't go away, then realised it was happening with every rom I flashed...
Hi guys,
I messed up. I made back ups using cwm. Not knowing they 're not compatible I then flashed twrp and then tried to load a rom that was hanging up using cwm thinking that would make a difference. It didn't it hung. I can't restore my backups cuz I don't have cwm. I have tried downloading the same rom many times thinking it was a bad flash. No go. I tried ROM][4.2.2][OFFICIAL] LiquidSmooth v2.9 - d2spr - 07|20|13 and that is not working either,. Phone won't even boot on.
What do I do? Please help.
Crap... phone won't even boot into twrp now. What do I do guys?
Calm down. Find a computer use odin to reflash cwm recovery or reflash back to stock rom. If you have a brand new S3 they have some type of new security. You will not be able to flash an aosp rom. They will all hang.
Have a great day!
edfunkycold said:
Calm down. Find a computer use odin to reflash cwm recovery or reflash back to stock rom. If you have a brand new S3 they have some type of new security. You will not be able to flash an aosp rom. They will all hang.
Have a great day!
Click to expand...
Click to collapse
Ed,
I cannot get into dwnld mode.
You have done the 3 finger power+vol down +home button at same time to get in download mode? Does the phone power on if not here http://forum.xda-developers.com/showthread.php?p=43724690
Have a great day!
edfunkycold said:
You have done the 3 finger power+vol down +home button at same time to get in download mode? Does the phone power on if not here http://forum.xda-developers.com/showthread.php?p=43724690
Have a great day!
Click to expand...
Click to collapse
Ed, yes I tried the three finger thing to get DL.
I am on that link you gave me and forgive me for double posting but I think this will get more activitiy.
here is what I posted:
I'm trying to do this fix.
I'm a lil confused...
I have a slax Linux cd and can boot in with bash #
when I type pwd it says i'm in /root
I try doing cd desktop where the debrick file is but it doesn't recognize my command.
Can I use slax? Do I need to put debrick on C:
Please. I have my 16gb sd card.... just need to get this image on and then move on from my bricked s3.
Thank you all in advance.
p.s I don't know ubunto and couldn't find a download for it.
Now since that post I put debrick_sph_l710.img onto C: to go along with /root slax reports it's in. No dice. I noticed the file is actually named debrick_sph_l710.img.xz on my computer. I tried using that extention and still no dice. Getting desperate here. I have ODIN ready to go with the tar file...I just need to get download on this phone. Please help.
Is slax no good to use ? Can you point me to another download of a unix boot disk?
In that thread there are different ways of doing it even with cygwin... Read through it. People there will help you. The SD card type is very important, seems high success with 16gig class 10 type.
Also this thread http://forum.xda-developers.com/showthread.php?p=43305728 which is where this method was pioneered. You need to be patient it's taken some people weeks to accomplish this.
Have a great day!
edfunkycold said:
In that thread there are different ways of doing it even with cygwin... Read through it. People there will help you. The SD card type is very important, seems high success with 16gig class 10 type.
Also this thread http://forum.xda-developers.com/showthread.php?p=43305728 which is where this method was pioneered. You need to be patient it's taken some people weeks to accomplish this.
Have a great day!
Click to expand...
Click to collapse
I dn't have weeks by no means. this is a sandisk 16gb. No idea what class..it doesn't say.
I've read the thread. It's very convoluted. Have you done this? What Linux boot disk did you use?
midnightmaraude said:
I dn't have weeks by no means. this is a sandisk 16gb. No idea what class..it doesn't say.
I've read the thread. It's very convoluted. Have you done this? What Linux boot disk did you use?
Click to expand...
Click to collapse
No I'm sorry I haven't done this. I have fortunately never bricked a device. No pun intended. But the answers are all there. I would be glad to help you seek your answers but I'm actually out with the wife and trying to assist you via mobile device.
Edit: here you tube video https://www.youtube.com/watch?v=6oDcYTMhNNg&feature=youtube_gdata_player
Have a great day!
midnightmaraude said:
I dn't have weeks by no means. this is a sandisk 16gb. No idea what class..it doesn't say.
I've read the thread. It's very convoluted. Have you done this? What Linux boot disk did you use?
Click to expand...
Click to collapse
I've tried cygwn too here's my posting output
[email protected] /cygdrive/c
$ sudo dd if=debrick_sph_l710.img.xz of=/dev/sdf
-bash: sudo: command not found
[email protected] /cygdrive/c
$ sudo dd if=debrick_sph_l710.img.xz of=/dev/sdf
-bash: sudo: command not found
[email protected] /cygdrive/c
$ sudo dd if=debrick_sph_l710.img of=/dev/sdf
-bash: sudo: command not found
[email protected] /cygdrive/c
Here is the way to try it in Windows http://forum.xda-developers.com/showthread.php?p=45276070
Keep in mind several have tried different types of SD cards but had no success until hey used a class 10. Some have had to write the image on the card several times before succeeding.
Have a great day!
I understand it is currently not possible to unlock a Razr M with 98.18.94 or 98.30.1 OTA. Never the less, I had been trying to restore a previous VooDoo root that I deleted before the last OTA. Through the experimenting, I screwed up the flash on my phone, and recovering it, I found something that might be interesting.
As others pointed out, downgrading does not work. Flashboot gives various errors. When I screwed up my file system, I was able to flash from 98.18.94 (which I had) to 98.30.1 (which was the only download I could find) using RSD Lite. I was lucky it worked. And since I have been able to experiment and keep flashing 98.30.1 over and over.
I would like to report that in my experiments, I noticed an interesting fact about the recovery.img:
I am able to flash stock 98.18.78 recovery to my phone running 98.30.1.
I have verified the recovery.img contents are not the same, according to a WinMerge file compare, they are ~10% the same
When I try to flash twrp or cwm recovery, the only fastboot error is to the effect "wrong partition size".
The size of .78 and 98.30.1 recovery are the same, 10,485,760 bytes
On the other hand, if I try to flash the .78 system.img fastboot, or use RSD lite to flash .78, I see different security related errors on the phone's fastboot screen- none of which mention partition size. Of course, this is related to the Locked Bootloader I have.
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Right now my Razr M has gone from 98.18.94 to 98.30.1 with a 98.18.78 recovery. And I'm working ok.
I am not a professional Android Dev. But I am going to do the research and try to modify a cwm type recovery to match the size of a Moto recovery, and see what happens.
I invite anyone with real experience to contribute.
Bryan
bryanwieg said:
What did you say?
Click to expand...
Click to collapse
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
aviwdoowks said:
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
Click to expand...
Click to collapse
I have already found that if I take the OTA recovery and unpackbootimg and then mkbootimg without changing anything.. it recompiles down to aprox 5mb, which is different than the size it started from Moto.
So I am looking at if the size is set in how the img is compiled.
30.1 and .94 are the same updates, just different system versions. As for the other stuff, I'm not even sure what to say. I'm with Avi on this, I definitely would like to see what a dev has to say.
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
aviwdoowks said:
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
Click to expand...
Click to collapse
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
bryanwieg said:
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
Click to expand...
Click to collapse
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
aviwdoowks said:
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
Click to expand...
Click to collapse
Well, you'r right on the money. I appended data to a CWM recovery the same as Moto did to thiers, including the certificate at the end.
I didn't get a partition size error this time, but I did get a 'Failed to hab check for recovery'.
Granted, I didn't manage to place the 'empty data' at the same point in the file as the stock roms did. Other than that, it must be the certificate.
bryanwieg said:
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Click to expand...
Click to collapse
No, because it first checks the size (or whether it's a valid image at all) and if the size is correct, it checks the signature.
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Really glad to see someone is still trying to find some sort of exploit for this device in it's updated state, it seemed like everyone had completely given up on it. My girlfriend recently grabbed a used Razr M to use for a while but it's fully updated, and I would love to be able to root it for her. I'll be following this thread to see if anything comes of this recovery downgrading
I'm pretty sure you can edit the props from what I can remember.
Sent from my XT907 using xda app-developers app
bryanwieg said:
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Click to expand...
Click to collapse
You can use root eplorer free to extract the single img from the 404 or 411 xml.zips
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Here http://sbf.droid-developers.org/phone.php?device=8
---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------
The razr hd (2), atrix hd, photon Q all use a recovery w/ same key. Git to work man!
Re:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
815turbo said:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
Click to expand...
Click to collapse
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
I am willing to try it out. Win 7 64bit... pass me needed staf to flash it
Sent from my XT907 using xda app-developers app
please do
815turbo said:
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
Click to expand...
Click to collapse
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
benya274 said:
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
Click to expand...
Click to collapse
I'll post it in just a few minutes. I will also post the required commands and we'll be backing up current recovery. If it fails, it should be no problem to restore your backed up recovery.
Download TWRP image on your phone from: titanroms.com/upload/rec.img
Please get to an adb prompt and run these commands:
su
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak2.img
Please ensure that both copies are 10MB. The dd command should end by saying "10485760 Bytes Copied" on all of the "dd" commands.
Now, you should have two backups of the recovery partition and the TWRP Image you downloaded from here all on your sdcard.
You can follow with these commands AFTER your backup has completed.
cp /sdcard/Download/rec.img /sdcard/rec.img
dd if=/sdcard/rec.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=twrprecbak.img
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.bak
reboot recovery
In the event of a failed attempt at this you can run the following from adb:
su
cd /sdcard/
dd if=/sdcard/recbak1.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give me a holler if you don't understand this well. Good luck, guys.
I am gonna try it out tomorrow,i dont have time to do it tonight cause i need to go to work. My pc on work does not have internet connection I will keep u guys posted on any progress.
Sent from my XT907 using xda app-developers app
Just wanted to say I flashed the old ICS recovery to mine using fastboot commands but it didn't get me very far though.if I then try and flash the corresponding blur zip from recovery it just says invalid signature. Was trying to find a way to downgrade so I could get rooted..
Sent from my XT907 using Tapatalk