Well, I loved this kernel! But I appear to have bricked when flashing another (also aparrently kernel fixed) rom.
I *could* get to CWM, but I can't touch system. The phone freezes if I try to do anything.
Odin will not flash.
I'm an experienced user, I've owned several Android phones in the past and understand how everything works, however, this time, it really appears I am dead.
I can take the phone back so no big deal, but I just wanted to let people know. If I am unable to get this working, it appears the new kernels still have some risk involved.
I was on UK Stock ICS (Not sure what the version was now), flashed Francos using DD, everything was fine but Wifi did not work, so I wanted to try Speedmod. This caused a bootloop. So I reverted, and the bootloop remained. At this point I downloaded a Lite rom that used Franco V4, (sorry, the name has escaped me) this flashed but also gave a bootloop. So I wiped, and re-applied.
When I reinstalled after wiping, the install bar glitched and flew past it's usual 100% right off the side of the screen. Then it froze.
After this I am unable to flash *anything* to the phone. CWM boots but I can't do anything within it. Odin attempts to flash but I see the phone send invalid responses back (non-alphabetical characters) and Odin then fails.
Anything else I could do? I think I've tried everything possible at this point. Gutted!
[edit]
UPDATE: This does currently appear to be a case of bad luck, and NOT The eMMC Bug. The eMMC Bug fix is now under critical testing by myself (as I have access to replacement phones within minutes), though I have flashed 18 times at present with no superbricks or broken eMMCs. So far so good!
I think u wiped from ICS kernel and this may have caused u a brick. At first when you flashed speedmod and had bootloop you could have flashed back to Abyss kernel wiped and reinstalled the whole rom instead of wiping from ICS kernel and installing rom. Its a known fact that while installing or restoring roms from ICS kernels people have faced lot of issues..
I'm aware of that issue. I used Franco's R5 kernel (which is ICS and superbug fixed. The fix was not a guaranteed fix, and sadly I appear to have proven this fix to be non-working at the moment.)
I guess I'll be popping back to the shop at lunchtime!
Cheers.
One last try just pull the battery for 30 seconds and try to get into download mode and try to flash stock GB with 16gb pit file and gb bootloaders
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
When i had Galaxy s same thing happened to me only download mode no cwm nothing and Odin was failing to flash stock roms even with a pit file and what i did was flash with bootloaders along with pit file and rom files and voila my phone was back to bussiness
You might be right about the PIT files. It would make sense, Odin almost completes when the phone throws out the invalid text- might be trying to put data out of the partition.
I'll give it a go, thanks. I do still have Download mode. I no longer can access recovery though.
so you cant flash on ODIN?? stuck on factoryimg??
Well, that didn't go to plan. Crashed again, and now I have no download mode, instead the phone appears to be insisting that the battery is not installed. How odd!
musashiro said:
so you cant flash on ODIN?? stuck on factoryimg??
Click to expand...
Click to collapse
This was the case, yes.
Oh, I just got Download mode back, Stupid thing. What odd behavior.
I can get the phone replaced within minutes if required (I'm 5 mins away from the shop) but I'd rather try to keep my internal storage intact
Here's the guide to fix it. I along with many others managed to fix our phones using this guide: http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
Thanks for that. I'd just found it before you posted and am reading through it now.
I am half tempted to try it, but I think if there are now "bad blocks" in internal memory, I will just get it swapped for a fresh device.
It's behaving weird, sporadically thinking the battery was removed etc. so I am not 100% sure this is a superbrick /mmc problem, and it could be some other issue that cropped up. Let's hope so (because I'd really like to think Superbrick is fixed as we had suspected!)
Thanks for your input. I'm off down the shops!
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
damiensturdy said:
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
Click to expand...
Click to collapse
Yes seems like a good plan to me, looking forward to get results from you soon.
Thanks
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Glad to have someone willing to risk their devices in these dark times. Well appreciated!
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
In order to run the test, you need to actually boot up the device, go through the settings, and install a few apps. Then go to recovery, and perform a wipe.
Simply hitting the Wipe key in succession (like 100 times) does not work. There must be something to format in the respective partitions.
Thank you for doing what you're doing. But if you could, and only if you have the time, could you try wiping from CWM (just wiping, not nandroid restore), for say 20 ~ 30 times? It's very tedious to do it due to the setting up and needing to wait for it to boot and install a few apps from the market.
I'm sure with 20 ~ 30 or more wipes on a single device, we can safely say that the fix is a likely permanent fix.
damiensturdy said:
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Click to expand...
Click to collapse
So, in short, you had /system corrupted at the filesystem level, not the eMMC level. This seems to be a common problem on the Note, and some people falsely describe it as "partial root". CM9's initramfs has had changes made to make it easier to fix these problems by not automatically mounting /system on entry into recovery.
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Good input guys. Thanks.
Yes, indeed this didn't appear to be the eMMC Bug. I can't guarantee what it was on the old phone (which did appear bricked.), I just know I started off the same. It's more likely that I knackered it with failed Odin flashes than the eMMC bug at this time.
I'm still flashing, installing, wiping, etc. I'm basically trying everything that we're not supposed to do. So far the worst I've got is a corrupt system partition (indeed, that is not an eMMC bug) but the only CWM able to fix that was Thors.
Basically if I knacker the phone I can get it replaced within minutes, so I might as well take advantage so that we can all relax knowing it's fixed (or continue to look for a fix if it isn't)
Obviously I shouldn't take the piss. If somehow I brick it a couple more times I'll be forced to stop. But I like to help so let's go! :-D
What does "flashed Franco from DD" mean? After that process did you ever verify that you where actually on Franco?
Perhaps the kernel flash didn't take and your subsequent wipes/flashes where from stock ICS kernel.
Sent from my GT-N7000 using xda premium
Entropy512 said:
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Click to expand...
Click to collapse
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
damiensturdy said:
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
Click to expand...
Click to collapse
That's because he kangs from CM and then releases warez based on our work.
Linux kernel without source code published = warez.
Related
I have the samsung galaxy S i9000m with bell mobility in Canada.
Earlier today my phone randomly hung for a long time, while not doing anything in particular (i had just passed through the lock screen). So I pulled out the battery. Upon trying to reboot the device, after the colourful SGS animation, it would just stop at a completely black empty screen. If the capacitive buttons were pressed, then they would light up and stay like that indefinitely. In addition the power button would not work, leaving pulling the battery the only way to reboot.
Not knowing exactly what was going on, I tried download and recovery modes to make sure they were still working. And in the clockwork mod recovery mode I tried to do a nandroid backup to see what would happen. It did not progress far before failing as a result of the system being unable to mount /data . I tried going into the mounting section specifically, and /data was not mounted. Upon trying to mount it manually, the same problem occurred, in which it was seemingly unable to access the partition.
Since then things have progressively gotten worse. Later on, when trying to boot, it would just hang at the black and white SGS logo (the one before the animation). For a period of time, when trying to boot normally, it automatically went into the recovery mode. But now it has resumed at just handing at the black and white SGS logo.
Furthermore, clockwork mod recovery no longer seems to be accessible (normally to get into clockwork mod, you do apply update.zip at the first recovery menu, but when you try to do that now it doesn't work.)
My device was rooted, and I very briefly tried the One click lag fix (purely out of curiosity at it's effect on quadrant scores, I didn't really have any problems with lag, and even my GPS felt fine), but promptly got rid of all traces of it afterward. ( I believe I not only deactivated it and uninstalled it, but also reverted to a previous nandroid backup)
I've also never flashed anything at all on the device. Though I am about to try flashing the JH2 rom from samfirmwares to see if that helps anything.
What do you guys think could be wrong, I have the inkling that it is a dead internal SD, but I am unsure of the symptoms of such (though messed up partitions definitely raises a flag in my head)? And as an aside, could someone familiar with bell verse me of the likely procedures in the event I have to return this phone?
Well thank you all for your council, hopefully I can salvage this great device T_T
P.S.:
I tried factory reset, but that failed due to not being able to access /data or whatever. . .
Hmm though interestingly enough, at my current stage, if I try to access adb shell I get the message:
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Fun, eh?
P.P.S
Even more goodness, now when I try to apply sdcard:update.zip it complains of not being able to mount /dev/block/mmblk0p1
So now seemingly it can't mount
/dev/block/mmblk0p1
/dev/block/mmblk0p2 ( i believe this was /data)
Not that you can eve get far enough for it to try to mount /data anymore
P.P.P.S
After flashing JH2, it has gone back to the point where it gets past all the logos and animations, and pretends to actually be able to work (that is, it seems like booting has finished, but we are left with a black screen that does nothing, and if you hit the capacitive buttons they stay on indefinitely. )
Well. . . after some initial recovery mode troubles (including a few times where I got an error upon entering recovery, and sometimes I didn't), though what had remained constant, was trying to utilize apply:sdcard update did not launch clockwork mod recovery.
Until now. Somehow magically the clockwork mod recovery has started existing again? Though the same /data mounting issues exist.
And with that, I am officially back to the initial problem stage Next step: trying to flash JPM i guess.
those are the symptoms of a corrupted sd card.
somewhere i read that it took a few flashes with odin to clear the sd card and get it working. have you tried flashing back to jh2 with repartition and a 512 pit? forget about froyo for now. i believe jh2 is a low level firmware, so it's your best option. good luck.
it has also been posted that using odin v1.3 with "android + spl" (not "gt-1000") in the title bar of the application helps. it took a few downloads before i got the correct one.
wang1chung said:
those are the symptoms of a corrupted sd card.
somewhere i read that it took a few flashes with odin to clear the sd card and get it working. have you tried flashing back to jh2 with repartition and a 512 pit? forget about froyo for now. i believe jh2 is a low level firmware, so it's your best option. good luck.
Click to expand...
Click to collapse
Yeah I have already tried flashing JH2 (see one of the later post scripts), and indeed with repartition and the 512 Pit. So I should repeat the process a few times?
And I seem to have odin 1.3 with GT-P1000 in the title bar. Well it seems you can change the title from the ini file, but furthermore odin 1.0 has the title you describe.
any updates i have the same problem im gonna die
try flashing back to JH2 with 813pit then try 512.. I got my SD working again after fooling around for about 3 hours with different pits and flashing different firmwares. JG8 and fooling around with the different pits and repartition it just started to work when I flashed 512 and JG8.. also you need to use odin v1.3.. clockwork will not help you now..
before this my SD was so bad I could not even use the 3 button combo to get into recovery.. my phone would just show the logo in a loop.. but I could still get into download mode. and just before that I got an error saying that it could not mount my internal SD.
SS2006 said:
any updates i have the same problem im gonna die
Click to expand...
Click to collapse
Well. . .at this point in time, i'm mainly contemplating how to return it.
I think I will try calling someone on the phone first so they can tell me what I need to do to exchange it. . .
Or I guess return it to the source, which is where I bought it. So sad Y_Y.
So yeah I am gonna just assume Internal SD failure. . . Quite peculiar.
edit:
Okies, I shall try using different PITs, I had tried JH2 and JPM firmwares, but I guess at this point I might as well just fiddle.
So what triggered the internal sd card corruptoin exaclty
the lag fix or JPM, or a bit of both
SS2006 said:
So what triggered the internal sd card corruptoin exaclty
the lag fix or JPM, or a bit of both
Click to expand...
Click to collapse
Neither actually :/ I did the lagfix multiple weeks ago, and then took it off 5 minutes later, and then did a nandroid restore to make sure. . .
And JPM was after it died. Its me fiddling around with firmwares to see if eventually something would work. . .
TriC_101 said:
try flashing back to JH2 with 813pit then try 512.. I got my SD working again after fooling around for about 3 hours with different pits and flashing different firmwares. JG8 and fooling around with the different pits and repartition it just started to work when I flashed 512 and JG8..
before this my SD was so bad I could not even use the 3 button combo to get into recovery.. my phone would just show the logo in a loop.. but I could still get into download mode. and just before that I got an error saying that it could not mount my internal SD.
Click to expand...
Click to collapse
yup i have the EXACT prob i cant get into recovery, but can get into download, and got the could no tmount
so what you did (and what im going to try now )
is JH2 813 pit, the nJH2 512 pit,
then JG8 and 512 pit?
Also u mean UGJG8?
did u have repartiion checked in ur odin or not
thanks btw
SS2006 said:
yup i have the EXACT prob i cant get into recovery, but can get into download, and got the could no tmount
so what you did (and what im going to try now )
is JH2 813 pit, the nJH2 512 pit,
then JG8 and 512 pit?
Click to expand...
Click to collapse
I also played around with jpk as well and flashed it with different pits. but yes in the end it was 512 and UGJG8 and repartition that got it working.
I was in the same boat as you thinking about returning it but then I was like what the hell and tried flashing different Roms and different combinations
JPM with 803
gets me past the boot lop into the galaxy s logo...
but thats it..dark screen, i can get into recovery now again, but it says can't mount
theres a 'format internal SD' option, but it says its not set up, so internal sd card is still toast
I know for a fact JG8 is doing nothing for me
the JG8 ur using is it the .tar file that has everything in it
TriC_101 said:
I also played around with jpk as well and flashed it with different pits. but yes in the end it was 512 and UGJG8 and repartition that got it working.
I was in the same boat as you thinking about returning it but then I was like what the hell and tried flashing different Roms and different combinations
Click to expand...
Click to collapse
so in your case what actually caused the corruption
SS2006 said:
so in your case what actually caused the corruption
Click to expand...
Click to collapse
just was using the phone.. opened my weather app.. then all of a sudden got a lot of force close pop ups for every app on the phone.. then the phone just rebooted the 1st time and it would load up then the screen would go black.. then I rebooted again and give me the can't mount error. then after I rebooted about 2 more times it would only go into download mode and I could not even get to recovery.. but its fine now.. been fine for about 3 weeks now..
Do you reckon using an external SD card would help,
if used with Clockwork?
TriC_101 said:
just was using the phone.. opened my weather app.. then all of a sudden got a lot of force close pop ups for every app on the phone.. then the phone just rebooted and give me the can't mount error. then after I rebooted about 2 more times it would only go into download mode and I could not even get to recovery.. but its fine now.. been fine for about 3 weeks now..
Click to expand...
Click to collapse
Did you have the lag fix installed, and were you on JPM
those are the 2 things I did right before I got into this loop of death
SS2006 said:
Did you have the lag fix installed, and were you on JPM
those are the 2 things I did right before I got into this loop of death
Click to expand...
Click to collapse
I just had JPK installed.. no lag fix was needed with that rom.. now that I think about it about an hour before my wallpaper had changed... I wish I remembered the combination of Roms and different pits I flashed to get it to start working again.. but I know I played around with it for 3 hours.
I do know other people have recovered theirs as well by flashing different Roms and pits.
Alright then, let the flashing begin
wish me luck
Hey just noticed your in London, Ontario as well. well ya good luck...
Alrigt, I randomly get reboots and I just rooted using Revolutionary last night. I'm using TWRP as my recovery and I want feedback as to if this is a normal issue or if it's just my handset. I hate sense and want rid of this garbage. >=( I appreciate all feedback, just don't be a jerk about it. I'm not new, and this isn't a noob question. I'm asking specifically about Revolutionary root with twrp then flashing CM7 as the rom and if it has bootlooping issues coming from stock.
I haven't tried TWRP, but you might want to try the usual recoveries, and try wiping everything once and and a fresh install. Just a thought. I have never had issues with any cyanogenmod. Oh another thing, might want to partition your SD card.
It's stuck in a bootloop right now. I actually already tried CWM and just did Amon_ra's recovery...it seems to be a CM7 issue with my phone? I'll try MIUI and then switch to CM7
So, you're afraid to ask for getting shot down.
I'm afraid to post an idea for getting shot down. But, I'll venture forth and probably be wrong. Do you still have PC136.img on your SD? If so, I think you're supposed to remove it. I could be wrong and probably am. I'm 70% sure I'll hear about it if so.
MIUI was bootlooping as well. I think this might be an issue with me flashing my splash screen after acquiring root?
Common issue: make sure you are wiping the SYSTEM partition. The "factory reset" wipe option does not do this. Or find one of those automated "super wipe" scripts to flash in recovery that does it all for you.
Others had bootloops and such and later posted back that it was a wipe issue.
Also, provide a logcat if you can.
Actually, I found that I had to wipe the boot partition for some reason. It worked and I hope this thread helps people get past boot loops. I also need to restore my Wimax keys now lol.
Ok, so to start off, I have resolved this, I am just trying to find out why it happened to prevent future occurrences. I was running Calkulin's EViO 3 v1.0, HBOOT 0.76, 2.15 Radio, Stock Kernel.
So here is what happened that led up to the problem. I had just downloaded the Latest amazon App of the day (x-Scope browser pro), and used the Reboot app that comes prepackaged with Calkulin's rom to reboot the phone. Upon restarting the phone got hung at the HTC EVO 4G screen (I let it sit here for about 15 minutes). My thought was ok, something is wrong with this app. So I booted into recovery to attempt to fix the problem.
Upon booting into recovery (Ra Recovery 2.3), I was greeted with
E:\ Can't mount CACHE:recovery/command
E:\ Can't mount CACHE:recovery/log
E:\ Can't mount CACHE:recovery/log
It took several minutes for these 3 errors to process on the recovery screen, every time I navigated to a new menu they would appear again. The first thing I did was wipe my Cache, and Dalvik. This removed the errors from the recovery, however the phone still wouldn't boot. So I ran VR_Superwipe and restored my CM7 nandroid. All is good now, however I would really like to know what caused this to happen in the first place.
I tried to google it, however it appears to be a very uncommon error to get, and of the posts I found with the same error people claimed it was unrecoverable and they had to run the RUU to fix it(This was not the case).
Somehow, someway, I believe either by the install of the app, and/or you had a corrupted rom install and that you just had bad timing! I've had the same situation happen to me.
Sent from Looney Tunes Central!
tazman1963 said:
Somehow, someway, I believe either by the install of the app, and/or you had a corrupted rom install and that you just had bad timing! I've had the same situation happen to me.
Sent from Looney Tunes Central!
Click to expand...
Click to collapse
Appreciate the reaponse. Yeah that seems to be what it looks like. I've been back on cm7 since that post with zero issues.
Sent from my PC36100 using Tapatalk
A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Uh oh. Working quickly between boots I unset the default on Apex launcher (since it updates frequently) and turned off the live wallpaper. I also shut off Wifi. No effect.
Next stop recovery. Cleared caches, etc. Nope. I had a fairly recent backup but took another one and it worked (whew). Decided that I would do a data wipe from recovery. Uh oh. Any attempt to format /data causes a crash.
I go to Odin to see if I can repartition flash. I can't find a PIT file for the P5113 but did find one for a 16K 7 inch model. Odin repartitioned it but still no joy. Wiping data causes a reboot. So does trying to restore a backup to /data.
Next stop Kies. You can tell it to reload firmware but you need your serial number which is written on the back of your tab (yes it is, it is about the height of a carbon atom). However, it asks you to enter "recovery" mode by pressing buttons that aren't on the tablet. I tried Odin mode but it couldn't connect. Using CWM recovery didn't work either.
So I decided I needed stock recovery. I could not find a P5113 stock recovery that wasn't bundled with an entire update package. So I unpacked an update package to get recovery.img. Flash_image didn't work (seems like it never works on this tablet, and now that I think about it, I think I wrote a thread on how to do it with dd that I forgot about last night! Duh: http://forum.xda-developers.com/showpost.php?p=31293383&postcount=32). Instead, I repacked just recovery.img with tar. Odin was able to flash this and I was back in the ugly stock recovery.
I never did try Kies though because I asked the stock recovery to reformat /data and it worked! Back to Odin to reflash CWM and then the backup I made Monday night rolled back on and I was back in business.
Restore my screen saver, redefault (is that a word?) Apex, and turn Wifi back on. Oh yeah, and run Triangle Away
So I'm not sure what to make of all this. Open questions:
1) Did I need to repartition? What's the right PIT file to use? I sure wish Odin could dump a clean image, but if it can, I don't know how.
2) What mode does Kies want? This could have been a VirtualBox problem but I got it to work before I got Kies installed on my wife's real Windows box (man Kies is slow!).
3) Why could stock recovery reformat /data but CWM could not?
4) Would it have been sufficient to just reflash the stock recovery, do the data wipe? I suspect so, but don't know.
Anyway.... things are back to normal. Love the tab, but sure wish these big companies wouldn't assume we don't know how to fix our own stuff and muck things up with "simplified" tools. By the way, this is the "touch" CWM that seemed to fail to fix /data. I did not try the normal one.
wd5gnr said:
A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Click to expand...
Click to collapse
Here we go again. Same problem but I'm not even getting into the boot. Does anyone know how to actually reformat and rescan flash for bad blocks? I have a feeling I have a bad flash block that is doing something evil.
Sigh.
Tried a different approach this time.
Booted to recovery and did an fsck on /data since it seemed to have the problem.
It did a lot of clean up and now I'm back up. Not sure what got damaged if anything though. Time will tell.
Good to hear that it is a happy ending, bro!
Sent from my AT1S0 using xda app-developers app
TLDR: See this post for the solution; but do read through the thread, lots of good info!
I've got a MB525 for parts, seller got rid of it because it won't boot up anymore. I've tried it and it shows black screen but it can be seen over USB and I can flash .sbf files. Now, I'm curious whether it can be made to work after all.
First I've tried most of the smgver=4 stock .sbf files but no luck, still got black screen. From what I've read, black screen means the efuse has blown to a higher version. So I tried the JORDN_U3_97.21.51 (smgver=5). Still nothing.
The only thing left would be to flash a Defy+ .sbf, I've seen people recommend DFP-231 Taiwan retail or similar, hopefully a smgver=6 or 7 would work.
I've no idea what the seller did to the poor thing, nor what ROM it came with originally or from where.
Am I right that I should try a Defy+ .sbf? On the one hand, no risk really, I got it for pennies so no big loss. On the other, it just irks me that a potentially fully working Defy should just be abandoned for scrap.
You can try it. But if your defy is green lens the camera won't work on stock Rom only on custom Rom CM10.....CM11.
Sent from my MB526 using Tapatalk
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
wirespot said:
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
Click to expand...
Click to collapse
Try DFP-231. If it works, you can go ahead with custom ROMs.
I've successfuly flashed DFP-231. By "successfuly" I mean it now shows the Moto logo and I can enter bootloader (version 10.00, FWIW) and the stock recovery.
But it won't go past the Moto logo, shows it for about 10 seconds and then it reboots, forever. I pulled the battery after ~10 reboots in a row.
Yes, I did a factory reset from recovery (ie. cache and data wipe).
Any idea what might be causing this or what else I can try?
Try to reflash sbf.
And say "bye" to your battery charging via phone.
I've been trying all kinds of DFP-231 .sbf images. So far no luck, still got a few to go. Some of them have a longer delay, such as the first Moto logo staying on for more than 10 seconds – some for 20-30 seconds... but eventually they all bootloop.
I have another Defy+ so I can charge the battery through that one, but why do you say I can't charge through this one anymore?
PS: I've just realized that the stock recovery can flash stuff from the SD card. Would it be ok if I take a nandroid backup and slap it in there? Does it matter from what kind of system the backup is from eg. stock, a CM version etc? Or will anything work?
For battery you can check lasts posts of my problem here http://forum.xda-developers.com/showthread.php?t=2568049... I have never solve it .
Try ti omap blank flash option in rsdlite
Stock recovery cannot help unless you can brute force or steal Motorola's private key
You could try making a custom sbf, which would include custom recovery, from where it could work out.
@sterver1 the battery issue is an exception, it does not occur for most
Sent from my MB526 using Tapatalk 4
Oh, so ok. I'm only unlucky...
Good luck...
Still no go unfortunately.
I tried DFP-231, including with TI OMAP blank flash option. If TI blank flash didn't work, am I looking at a hardware problem?
To recap: it's a MB525 (unknown whether red or green) stuck in bootloop: will show Motorola logo for ~10 seconds then restart and repeat forever. I can enter bootloader and flash SBFs but so far none of them helped. I can enter stock recovery and wipe /data and /cache, still no help from there. It was already at BL7 when I got it (tried lower versions first and got blank screen, only BL7 will allow it to boot).
Cannot flash ZIPs from stock recovery because it will only accept ZIPs signed with Motorola's private key which I obviously don't have.
I've read that the wrong region SBF might be the bootloop cause so I will still try out the rest of the official BL7 SBFs, just in case.
The only thing left I can think of is to somehow put custom recovery in there so I can try flashing a custom ROM.
But how do I build a custom SBF with 2ndinit and CWM or TWRP? I have the unpacker and I know how to unpack and repack a SBF. I also know that CG39 is an ext3 image of the /system partition, but that's about it. Which CG files do I have to modify and how?
I'm also not clear on what a "fixed SBF" is. I've noticed that it usually contains only certain CG files, but not sure how it works together with other types of flash and what good are they.
You can flash one of the cm 10 sbfs in the dev forum. Basically you need the sbf to contain the boot menu and recovery to try flashing from custom recovery. A fixed sbf is used to prevent bl version from incrementing by removing the higher version files
Sent from my MB526 using Tapatalk 4
I did it! The SBFs that did the trick are the ones in the OP in the thread Motorola defy bl7 sbf all in one. First the Asian Retail BL7, then wipe from stock recovery, then the MIUI SBF (which also contains CWM custom recovery). Then it booted right up.
I'll be back with more info about this Defy just returned to the land of the living after I poke around a bit (the MIUI ROM is in Chinese, gotta figure out how/if I can switch to English...)
So! Once again it's been proven that it's nearly impossible to softbrick a Defy. Given enough obstinacy ^_^ you can find a SBF that will put it right again.
PS: I should probably also add to the wiki page various stuff I've learned while doing this. I've had a hard time looking up some info, maybe it will help others.
Aaaand I spoke too soon. It booted MIUI successfuly exactly once (1 time). Now after the Moto logo dissapears I get a blank screen (but lit, not off) and nothing happens. I also tried a CyanogenMod ROM (Quarkx), both 10.0 and 10.2 – the CM spinning logo appears, it goes on for a while, sometimes it attempts to boot (got to the Dalvik generation, for example) but then it reboots, other times it will keep spinning and nothing happens.
On the bright side, I now have access to the advanced bootloader and custom recovery with all the goodies (ADB shell etc.) which opens up possibilities. If anybody has any ideas what I could try to diagnose this, please speak up – like I said, I can now have access to the actual Linux system on the phone.
The only idea that pops to mind right now is the CPU settings. Maybe it got overclocked by the original owner and something got fried? Resetting them to defaults didn't seem to do anything.
Still no luck. The MIUI I linked above is the only one that boots up, but won't recognize the SIM card and claims there's no GSM connectivity.
I'm speculating that perhaps something is messed up with the radio hardware, and that MIUI is the only ROM that somehow works around that and boots up, but the other ROMs don't expect it and reboot halfway through the bootup sequence.
I'll see if there's any logs made during bootup.
The reboots are characteristic of bad eMMC(data not getting wiped properly). Does miui work fine apart from radio? Also 2ndboot builds require a specific stock kernel(from eu dfp 231) so try that as well. Try full wipes from cwm, and make sure the data partition is formatted correctly from boot menu(ext3 for ics and below, ext4 for jb+).
The miui sbf masked the data problem(atleast temporarily) allowing the phone to boot up. Unfortunately if you do have other /data issues(which are seemingly unrelated), they all point at bad eMMC, necessitating replacement of the motherboard as the only viable option.
Sent from my MB526 using Tapatalk 4
@thekguy: Yes, apart from the GSM MIUI seems to be working fine, including WiFi. But only one time, if I reboot it doesn't start up again. Sometimes I get a hanged boot logo, sometimes I get endless bootloops. Other ROMs never work, it's straight to hanged or bootloop.
Are you saying that the internal memory has gone bad, like an HDD getting bad blocks? If that's the case, I can probably use a recovery update script to repartition the memory and work around the bad zone(s). As long as I can figure out which exactly are the bad zones (other than trial and error).
Or are you saying it's simply not getting scrubbed properly and it's a problem with the filesystem? In which case I can reformat at least some of them (/system, /data/ and /cache).
But doesn't the flash tool overwrite the partitions by raw-dumping images on them? So how can a bad filesystem survive SBF flashing?
And what about update zips? Do they reformat/raw-dump partitions – or do they just take the filesystem for granted and copy to it?
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
thekguy said:
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
If the bad eMMC blocks are entirely within the ext3/4 partitions, we should be able to run badblocks on them (taking care not to overwrite the signature at the end of /dev/block/mmcblk1p21 but past the actual file system) and avoid them. As the badblock list is stored in the file system rather than the partition table, I believe that would work.
I've also been experimenting with using an SD card partition for /system and keeping only a few minimal files on the eMMC (I think we could get away with busybox and a modified logwrapper script)—no unexpected problems. It's quite likely those two files won't interfere with the bad blocks, and after they've booted the kernel we wouldn't be touching the eMMC at all (assuming /data and /cache are also SD partitions, but that should be doable). I have been using Quarx's CM11, and I don't think my trick works with stock ROMs (at least I've never had success booting a stock kernel with 2nd-boot), so it might not be a helpful suggestion.
2nd system/ multiboot is a good idea to get past the bad blocks (probably some performance hit though) but better than a non functional phone. 2nd system should work even with a stock ROM as secondary system, not sure why it isn't working for you. I have no idea about the badblock remapping logic
Sent from my MB526 using Tapatalk